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

cherrypick-2.0: storage: fix decommissioning of absent node #23378

Merged
merged 1 commit into from
Mar 6, 2018

Conversation

tbg
Copy link
Member

@tbg tbg commented Mar 5, 2018

Cherry-pick of #23082.

When a node is decommissioned in absentia, the gateway node may not be
aware of its most recent liveness entry. Before this bug fix, the
gateway would fail the decommissioning process. Instead, we now read the
liveness record from the KV store in this path.

Fixes #17995.

Release note (bug fix): Decommissioning a node that has already been
terminated now works in all cases. Success previously depended on
whether the gateway node "remembered" the absent decommissionee.

When a node is decommissioned in absentia, the gateway node may not be
aware of its most recent liveness entry. Before this bug fix, the
gateway would fail the decommissioning process. Instead, we now read the
liveness record from the KV store in this path.

Fixes cockroachdb#17995.

Release note (bug fix): Decommissioning a node that has already been
terminated now works in all cases. Success previously depended on
whether the gateway node "remembered" the absent decommissionee.
@tbg tbg requested a review from a team March 5, 2018 18:28
@cockroach-teamcity
Copy link
Member

This change is Reviewable

@tbg tbg merged commit 59ec918 into cockroachdb:release-2.0 Mar 6, 2018
@tbg tbg deleted the cp20/decom-absent-node branch March 6, 2018 01:44
@tbg tbg restored the cp20/decom-absent-node branch April 16, 2018 15:23
@tbg tbg deleted the cp20/decom-absent-node branch May 8, 2018 15:06
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