-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Retry logic if a worker is down #1128
Projects
Comments
This is fixed in the latest version which uses agent <> server communication. The agents implement a heartbeat, and if enough time passes without any communication, the build is pushed back to the front of the queue for re-processing. So I think we have this failure scenario covered now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When you add multiple Docker daemons from multiple hosts, if one of the hosts drop out you end up with a 1/n build failures due to time out.
It would be ideal, if there were retry logic after the time out to drop the build back on the queue. Additional optimization would be to keep track of workers that are unresponsive and eject them from the pool. Just to save on build startup time.
The text was updated successfully, but these errors were encountered: