You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we run browser nodes separately they are autoscaling as expected. For example, if we run the Firefox test the Firefox nodes are scaling as per the count in the session queue.
But the issue is when we start multiple browser tests eg: Chrome, and Firefox together then at a time only one browser is autoscaling.
The other browser will stay in the queue until all current running browser sessions are finished.
Once all the running sessions are finished the pending browser session will start to autoscale.
The below screenshot shows the chrome sessions are pending in the queue.
Keda version : 2.7.2
Expected Behavior
Both Chrome and FF should autoscale simultaneously as per their session count in the queue.
Actual Behavior
Only one browser is autoscaling (here FF) at a time, the other one is waiting in the queue
Steps to Reproduce the Problem
Logs from KEDA operator
example
KEDA Version
Other
Kubernetes Version
v1.20.15
Platform
Amazon Web Services
Scaler Details
selenium-grid
Anything else?
No response
The text was updated successfully, but these errors were encountered:
@ChandniSuresh Are you positive on your version? Not sure if a version 2.7.2 exists from what I can see but 2.8.0 had a few bug fixes for selenium grid that you should probably check out:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.
stalebot
added
the
stale
All issues that are marked as stale due to inactivity
label
Nov 28, 2022
Report
When we run browser nodes separately they are autoscaling as expected. For example, if we run the Firefox test the Firefox nodes are scaling as per the count in the session queue.
But the issue is when we start multiple browser tests eg: Chrome, and Firefox together then at a time only one browser is autoscaling.
The other browser will stay in the queue until all current running browser sessions are finished.
Once all the running sessions are finished the pending browser session will start to autoscale.
The below screenshot shows the chrome sessions are pending in the queue.
Keda version : 2.7.2
Expected Behavior
Both Chrome and FF should autoscale simultaneously as per their session count in the queue.
Actual Behavior
Only one browser is autoscaling (here FF) at a time, the other one is waiting in the queue
Steps to Reproduce the Problem
Logs from KEDA operator
KEDA Version
Other
Kubernetes Version
v1.20.15
Platform
Amazon Web Services
Scaler Details
selenium-grid
Anything else?
No response
The text was updated successfully, but these errors were encountered: