What happened?

I did run a selenium standalone server, after the system powered on again from standby the standalone server was not functional.
After looking into the logs and the code i think GridModel.purgeDeadNodes was called by the 30s intervall before the heartbeat did update the timestamp in nodePurgeTimes.

It looks like there are two concurrent strategies to remove the deadNodes. One is X health checks failed will remove the node and one is time based. The time based strategy is failing in this case and will remove the only node for the standalone server.

This might be an edge case, but would like to share it here.

PS: In this state the UI is showing 'Loading ...' constantly

How can we reproduce the issue?

Send the system into standby, right after the heartbeat did nodePurgeTimes for more than 30s and power it on again and hope for `GridModel.purgeDeadNodes` to run :D

Relevant log output

09:40:20.401 INFO [GridModel.release] - Releasing slot for session id dec0a19e82c52ca30bb6179848cd5aa6
09:40:20.402 INFO [SessionSlot.stop] - Stopping session dec0a19e82c52ca30bb6179848cd5aa6
14:35:18.655 INFO [GridModel.purgeDeadNodes] - Switching Node http://127.0.0.1:64231 from UP to DOWN
14:35:18.658 INFO [GridModel.purgeDeadNodes] - Removing Node http://127.0.0.1:64231, DOWN for too long

Operating System

Windows 10 x64

Selenium version

Java 4.8.2

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

chrome 112

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

chromedriver 112

Are you using Selenium Grid?

Standalone 4.8.2