Skip to content
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

loss of quorum recovery: half-online approach #77273

Closed
aliher1911 opened this issue Mar 2, 2022 · 0 comments
Closed

loss of quorum recovery: half-online approach #77273

aliher1911 opened this issue Mar 2, 2022 · 0 comments
Assignees
Labels
A-kv-replication Relating to Raft, consensus, and coordination. C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)

Comments

@aliher1911
Copy link
Contributor

aliher1911 commented Mar 2, 2022

As outlined in RFC next stage would be to collect replica info from the running cluster without doing stop the world.

This should be built on the foundation of what we already have. Use existing infrastructure to plan and update replicas, but move collection to a distributed operation that would provide the necessary info.

Jira issue: CRDB-13511

Epic CRDB-14205

@aliher1911 aliher1911 added C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) A-kv-replication Relating to Raft, consensus, and coordination. T-kv-replication labels Mar 2, 2022
@erikgrinaker erikgrinaker changed the title loss of quorum recovery: half-online approach loqrecovery: half-online approach Sep 28, 2022
@exalate-issue-sync exalate-issue-sync bot changed the title loqrecovery: half-online approach loss of quorum recovery: half-online approach Nov 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-kv-replication Relating to Raft, consensus, and coordination. C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
Projects
None yet
Development

No branches or pull requests

1 participant