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.

Sign up for GitHub

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

Jump to bottom

kvserver: ability to re-initialize Raft node #104322

Closed
erikgrinaker opened this issue Jun 5, 2023 · 2 comments
Closed

kvserver: ability to re-initialize Raft node #104322

erikgrinaker opened this issue Jun 5, 2023 · 2 comments
Assignees
@erikgrinaker
Labels
C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)

Comments

@erikgrinaker
Copy link
Contributor

erikgrinaker commented Jun 5, 2023 •
edited by exalate-issue-sync bot
Loading

Raft is generally configured on startup, via environment variables. In order to support dynamic configuration, we should have infrastructure to re-initialize the Raft RawNode on demand, by taking out raftMu and replacing internalRaftGroup. There should also be convenience functions to do this across all local replicas, with pacing. This is primarily motivated by version-gating CheckQuorum, and dynamically enabling it once the 23.2 upgrade is finalized (see #104189 (comment) and #104042).

Jira issue: CRDB-28466

Epic CRDB-25199
@erikgrinaker erikgrinaker added C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) T-kv-replication labels Jun 5, 2023
@erikgrinaker erikgrinaker self-assigned this Jun 5, 2023
@blathers-crl
Copy link

blathers-crl bot commented Jun 5, 2023

cc @cockroachdb/replication

@erikgrinaker erikgrinaker mentioned this issue Jun 5, 2023
Merged
@erikgrinaker
Copy link
Contributor Author

erikgrinaker commented Jun 8, 2023 •
edited
Loading

This won't be necessary right now, see #104042 (comment).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@erikgrinaker erikgrinaker

Labels
C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@erikgrinaker