-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: Consider maxSessions in Selenium Grid Scaler #2774
fix: Consider maxSessions in Selenium Grid Scaler #2774
Conversation
Signed-off-by: Alejandro Dominguez <adborroto90@gmail.com>
Signed-off-by: Alejandro Dominguez <adborroto90@gmail.com>
/run-e2e selenium* |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Only small nits inline.
Thanks a lot for this contribution!
/run-e2e selenium* |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Signed-off-by: Ram Cohen <ram.cohen@gmail.com>
Signed-off-by: Alejandro Dominguez adborroto90@gmail.com
Consider grid
maxSession
to scale Selenium Grid. Since each node can handle a number of parallel sessions defined bymaxSession
then is not needed to scale for each pending session.Example: if maxSession=5 each node can hold up to 5 concurrent sessions. Therefore, if there are 10 requests in the queue, only 2 nodes are necessary to fulfill the requirements. Currently, the Selenium Grid Scaler of KEDA will scale up to 10 nodes in this case, ignoring the maxSessions per node.
Documentation changes: PR
More info:
Checklist
Fixes #2618