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
Consul KV consistency checks #894
Conversation
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 |
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,
orchestrator
could run a consistency check against its local KV store to detect and resolve such inconsistency.Initial commit: writing Nano timestamp in all KV stores.