Maybe the fancy solution is to have all of the hubs communicate to each
other, or a central dashboard that can query the Hubs to give a 'bigger
picture' view of the grid.
As a poor mans solution I would like to plop a load balancer in front of
*What I know* (correct me where I'm wrong)
In order to do that I need some sort of session stickiness.
Selenium/Grid isn't using sessions (in the JEE sense) it is using an
internal Test Session passed along in the url.
To accomplish this I'll need to do 2 things:
1) Identify all paths where that Session is passed along
2) Make that session uniquely tied to the hub so the loadbalancer can
identify which hub to route it to.
In Hub I see a number of servlets being registered.
- Is there any docs on the possible args passed to each (or do I have to
dig thru each servlet and map it myself?)
- Most important: When an actual test is being run, it appears that it is
going thru the DriverServlet (usually via
Are there other places that session is passed along?
Basically I'm trying to identify all urls where that session might be
passed in so I can make the load balancer understand them and also the
second half of