Grid 4. Unable to limit number of maxSession within node via passing NODE_MAX_SESSION=3

[seoslav]

🐛 Bug Report

Grid 4. Unable to limit number of maxSession within single node via passing NODE_MAX_SESSION=3 either on hub or node level.

To Reproduce

Detailed steps to reproduce the behavior:

1. Create hub
   docker run -d -p 4442-4444:4442-4444 -e NODE_MAX_SESSION=3 -e NODE_MAX_INSTANCES=1 -e GRID_MAX_SESSION=5 --net grid --name selenium-hub selenium/hub:4.0.0-alpha-7-prerelease-20201009
2. Create at least one node:
   docker run -d --net grid -e SE_EVENT_BUS_HOST=selenium-hub -e SE_EVENT_BUS_PUBLISH_PORT=4442 -e SE_EVENT_BUS_SUBSCRIBE_PORT=4443 -e NODE_MAX_SESSION=3 -e NODE_MAX_INSTANCES=1 -v /dev/shm:/dev/shm selenium/node-chrome:4.0.0-alpha-7-prerelease-20201009
3. Check status page:
   "value": { "ready": true, "message": "Selenium Grid ready.", "nodes": [ { "id": "a07dfee7-5136-4753-beb6-53c791536c83", "uri": "http:\u002f\u002f172.22.0.3:5555", "maxSessions": 4, "slots": [

Expected behavior

MAX_SESSION=3

Environment

OS: Windows 10
Browser: Chrome
Selenium Grid version (if applicable): 4.0.0

[raju249]

Hi @seoslav 👋

Thanks for the issue. I think this is fix on the docker config. We support an option as --max-sessions but the docker config for Hub and Node uses max-session which is incorrect.

/cc - @diemol

[omarmhaimdat]

I am still experiencing the same issue, and nothing works. The "maxSessions" variable is always set up at 2. Tested on firefox and chrome. I'm using the docker-compose-v3-full-grid.yml file.

[youssefqarri]

I am facing the same issue from my side.

[diemol]

I just fixed this in the main repository, and it will be released in the next couple of days. Please keep an eye on the releases for this repo.

[anandshende06051994]

Hey, any updates on this?

[diemol]

This was already fixed and released. Please check the most recent release.