[🐛 Bug]: After adding an extra node to the grid I am seeing 5 on the browsers instead it should be 8

[abhi-iac]

What happened?

I have today added an extra node to the hub and on the UI I am seeing the extra node but the problem is I am not seeing 8 onto of browsers stereotype, I am seeing only 5. Attaching screenshot for reference

How can we reproduce the issue?

Not sure how you can replicate the issue but if you add an extra node to hub you might see.

Relevant log output

Attached screenshot for reference

Operating System

Windows server 2019 Datacenter

Selenium version

openjdk 11.0.16.1 2022-08-12 LTS

What are the browser(s) and version(s) where you see this issue?

Chrome 130.0.1

What are the browser driver(s) and version(s) where you see this issue?

Chrome Driver 129.6668.89

Are you using Selenium Grid?

Selenium grid 4..24.0

[github-actions]

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

---

Info for maintainers

Triage this issue by using labels.

If information is missing, add a helpful comment and then I-issue-template label.

If the issue is a question, add the I-question label.

If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted label.

If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C), add the applicable G-* label, and it will provide the correct link and auto-close the issue.

After troubleshooting the issue, please add the R-awaiting answer label.

Thank you!

[VietND96]

What is TOML config that you provided to Node

[VietND96]

Also, by default, --override-max-sessions is false. Without enabling it, max sessions will not take effect. And max sessions will be detected based on number of processors by default. Read this https://www.selenium.dev/documentation/grid/configuration/cli_options/#node

[abhi-iac]

Yes, just realized that max-session in the TOML to 5, it suppose to be 8. Thanks for your reply :)

[github-actions]

This issue has been automatically locked since there has not been any recent activity since it was closed. Please open a new issue for related bugs.