This repository was archived by the owner on Feb 18, 2025. It is now read-only.
Merged
Conversation
added 2 commits
May 21, 2019 07:58
Collaborator
Author
|
What this PR turned to be doing: Assuming There's caching to avoid abusing consul. On first iteration as leader, What this effectively does: if a consul cluster was down for any reason, and if some failover took place at that time, and as result |
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
Work in progress to be able to audit and fix KV pair inconsistency, especially external KV pair store inconsistencies.
e.g. if upon failover Consul is unavailable,
orchestratorcould run a consistency check against its local KV store to detect and resolve such inconsistency.Initial commit: writing Nano timestamp in all KV stores.