Skip to content
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

Selenium Grid Scaler | Multiple browser nodes are not scaling parallel #3620

Closed
ChandniSuresh opened this issue Sep 1, 2022 · 3 comments
Closed
Labels
bug Something isn't working stale All issues that are marked as stale due to inactivity

Comments

@ChandniSuresh
Copy link

ChandniSuresh commented Sep 1, 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.
image

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

@ChandniSuresh ChandniSuresh added the bug Something isn't working label Sep 1, 2022
@Wolfe1
Copy link
Contributor

Wolfe1 commented Sep 29, 2022

@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:

https://github.com/kedacore/keda/releases/tag/v2.8.0

#2709
#3061

The 2nd of the two issues I think may be the issue for you.

@stale
Copy link

stale bot commented Nov 28, 2022

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.

@stale stale bot added the stale All issues that are marked as stale due to inactivity label Nov 28, 2022
@stale
Copy link

stale bot commented Dec 5, 2022

This issue has been automatically closed due to inactivity.

@stale stale bot closed this as completed Dec 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working stale All issues that are marked as stale due to inactivity
Projects
Archived in project
Development

No branches or pull requests

2 participants