Irregular behavior of Grid

[lukeis]

Originally reported on Google Code with ID 8379

To reproduce the problem.

Start a grid on first machine - hub A (Windows) (2.42.2)
Start a grid on second machine - hub B (Linux) (2.44.0)

Register a node with (any browser) to hub A. (2.42.2)

Wait for the node to be registered and displayed on the selenium console page.

Now, this is the trick -> shut down the node (Ctrl+C) and quickly change the hub address
to hub B (don't change the nodes port) and start the node.

Result: the node gets registered to both hubs (A and B) and test can be executed pointing
to any of the hubs. Is it a feature that allows execution of tests from any of hub
on a single node. : ) 
Its not a problem, but it is just a irregular behavior in my perspective.

Reported by varun.tyagi.hrgi on 2015-01-13 12:43:26

[lukeis]

Yes, it is a sort of feature :)

When a node loses connection to a hub it stops sending 'heartbreaks'. But the hub has
memory. It knows there is a node on the given port, and it attempts to redirect requests
to this node for some time. And it stops utilizing the node after missing the next
heartbreak only. I suppose this timeout is configurable, but in real grids you hardly
want to make it very short.

Reported by barancev on 2015-01-17 23:04:00

• Status changed: WontFix
• Labels added: Component-Grid

[lukeis]

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

• Labels added: Restrict-AddIssueComment-Commit