This repository has been archived by the owner on Jul 27, 2023. It is now read-only.
Increase the time waiting for a consul leader to be elected #1648
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Attempts to address #1625 |
|
all builds passed (aws failed but only due to a timeout during cleanup - the actual build and health checks passed) |
|
@ChrisAubuchon @ryane Nice! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When the consul leader is restarted by the consul-rolling-restart.sh, the unlocking of the
locks/consulnode can fail with500because the Consul cluster isn't quite ready despite the/v1/status/leaderconsul endpoint reporting that there is a leader. Increase the time waiting for the cluster to settle.