Grid Console dead locks if nodes are unreachable

[lukeis]

Originally reported on Google Code with ID 8002

Took me a while to figure this one out. When the console HTML page is rendered, it tries
to reach out and check on the status of every grid node. If you have 10 nodes and 5
of them go offline, the console will try to reach into each node individual, timeout,
move to the next node.

Because of this, the console can quickly become un usable if you have nodes drop off
for a reboot. This issue can be fixed by providing a REST api and some JS to make these
updates async so the whole page does not lock up if a couple of nodes went offline.


I'd like to fix this issue after finishing the REST api, so this issue is documentation.

What steps will reproduce the problem?
1. Create grid with 10 nodes
2. Kill off 1/2 of the nodes abruptly
3. Navigate to console

What is the expected output? What do you see instead?
Console should still load even if nodes is not present.


Selenium version: 2.43.1 and <
OS: Any
Browser: Any
Browser version: Any


Work in progress to fix this here https://github.com/dimacus/selenium/tree/api

Reported by Dima.Kovalenko on 2014-10-07 17:56:57

[lukeis]

Reported by barancev on 2014-10-08 10:24:53

• Labels added: Component-Grid

[lukeis]

Reported by luke.semerau on 2015-09-17 17:47:06

• Labels added: Restrict-AddIssueComment-Commit