Add retry on consul lock if failures #74
Closed
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
Since consul lock is based on consul infrastructure, we can hit issues when consul is restarting while locking choregraphie on consul. Indeed, we had cases where consul on leader node took times to restart causing Diplomat call failure.
mougams
force-pushed
the
retry_on_consul_failure
branch
from
5b19b4a to
677c0d1
Compare
|
Replaced by #75 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Since consul lock is based on consul infrastructure, we can hit issues when consul is restarting while locking choregraphie on consul. Indeed, we had cases where consul on leader node took times to restart causing Diplomat call failure.