This repository has been archived by the owner on Dec 5, 2017. It is now read-only.
Admin command timeouts #153
Milestone
Comments
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
it's possible that doozer could be stale and offline nodes could still be in there, admin commands will hang trying to connect to it.
We should have a reasonable timeout and move on to the next matching instance, we might also want to deregister the instance then because we are unable to connect to it, it must be dead
The text was updated successfully, but these errors were encountered: