-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enhancement: safe shutdown #12
Comments
Seems to be a good idea. I think current implementation is here: https://github.com/seleniumkit/gridrouter/blob/master/proxy/src/main/java/ru/qatools/gridrouter/PingServlet.java because in fact Selenograph wraps GridRouter code and adds more features. |
@vania-pooh can the grid-router can work behind load-balancer like selenograph? |
@Shnitzelil sure. The main difference is the absence of MongoDB, extended stats and UI. The main advantage - it's stateless. |
Should this be a different API not braking the Gridrouter API... |
Summon @smecsia. |
@Shnitzelil Yes, we need to change the Gridrouter code to affect Selenograph this way. Send a PR to Gridrouter repository and we'll rebuild Selenograph with the newer features. |
My current architecture is
Two Selenograph services behind hardware load balacner (checking the /ping API status code)
When I wish to restart one of the machines I would like to stop it gently...
my suggestion is to change the return status code from the /ping API to be 5xx or 4xx
Or to change the return value from ok to something else (like "shunting down" or whatever).
Once no new connection will arrive it will be fully shutdown.
Or any suggestion you have...
WDYT?
The text was updated successfully, but these errors were encountered: