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

release-21.1: kvserver: handle dead/decommissioning non-voters #62405

Merged

Conversation

aayushshah15
Copy link
Contributor

Backport 2/2 commits from #61682.

/cc @cockroachdb/release


The PR is very similar to #59403.

Previously, non-voters on dead or decommissioning nodes would not get
removed or replaced. This commit fixes this behaviour.

Resolves #61626

Release justification: fixes limitation where dead/decommissioning
non-voters would not be removed or replaced
Release note: None

…voters

This commit teaches the allocator to emit actions to repair a range by
removing/replacing dead or decommissioning non-voters.

Release justification: needed for non-voting replicas
Release note: None
The commit is very similar to cockroachdb#59403.

Previously, non-voters on dead or decommissioning nodes would not get
removed or replaced. This commit fixes this behavior.

Release justification: fixes limitation where dead/decommissioning
non-voters would not be removed or replaced
Release note: None
@aayushshah15 aayushshah15 requested a review from a team as a code owner March 22, 2021 23:59
@cockroach-teamcity
Copy link
Member

This change is Reviewable

@aayushshah15 aayushshah15 changed the title kvserver, allocator: emit actions to handle dead/decommissioning non-voters release-21.1: kvserver: handle dead/decommissioning non-voters Mar 23, 2021
@aayushshah15 aayushshah15 merged commit 7ea43d6 into cockroachdb:release-21.1 Mar 23, 2021
@aayushshah15 aayushshah15 deleted the backport21.1-61682 branch March 23, 2021 04:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants