Skip to content

[🐛 Bug]: Issue with Scaling Already Scaled Deployments #2464

@Doofus100500

Description

@Doofus100500

What happened?

Hi, thank you so much for refactoring the grid scaler, it’s really awesome. However, I’m noticing issues with scaling already scaled deployments. Here’s an example:

I request 10 sessions, and 10 pods with browsers are launched. Then I request an additional 20 sessions, but only 10 more pods are added to the existing ones. This results in 10 sessions remaining in the queue until the previous sessions are completed.

I think the scaling logic should work as follows: if there are already 10 pods running, then when 20 more sessions are queued, the total should scale up to 30 pods.

keda version: v2.16.0

image

Command used to start Selenium Grid with Docker (or Kubernetes)

helm

Relevant log output

add a screenshot from grafana

Operating System

k8s

Docker Selenium version (image tag)

4.26.0-20241101

Selenium Grid chart version (chart version)

0.37.1

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions