[🚀 Feature]: Greedy Slot Scheduler Algorithm

[kumarsourav12]

Description

Can we get a test scheduler algorithm that follows a greedy approach? Currently, the default scheduler follows a round robin-like approach to scheduler testing. But in some cases, we would want to saturate one node before moving to a new node. This is going to help us in scenarios where we have custom auto-scaler for the Selenium grid.

Have you considered any alternatives or workarounds?

No response

[selenium-ci]

@kumarsourav12, thank you for creating this issue. We will troubleshoot it as soon as we can.

Selenium Triage Team: remember to follow the Triage Guide

[VietND96]

The current default slot selector you can refer to the explanation here https://github.com/SeleniumHQ/selenium/blob/9f6c0fe4a4525b749be5f03abbd5a785be7bac8c/java/src/org/openqa/selenium/grid/distributor/selector/DefaultSlotSelector.java

[pujagani]

If you want to create a custom slot selector and use that, you can do so and pass it to the Grid using "--slot-matcher" option.

selenium/java/src/org/openqa/selenium/grid/distributor/config/DistributorFlags.java

Line 71 in 6a58efb

names = {"--slot-matcher"},

[VietND96]

As per #15897, the usage: pass value to CLI option --slot-selector when starting Distributor (or Hub/Standalone), or similar in TOML config
For example: --slot-selector org.openqa.selenium.grid.distributor.selector.GreedySlotSelector