-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
storage: fix decommissioning of absent node #23082
Conversation
Review status: 0 of 2 files reviewed at latest revision, all discussions resolved, some commit checks failed. pkg/storage/node_liveness.go, line 276 at r1 (raw file):
Why don't we create a new method to retrieve the liveness instead of this obscure approach of sending a cput and hoping for the condition failed error? I don't think we need the retry logic in Comments from Reviewable |
Review status: 0 of 2 files reviewed at latest revision, 1 unresolved discussion, some commit checks failed. Comments from Reviewable |
e5cd0c3
to
4381f4e
Compare
TFTRs! Review status: 0 of 2 files reviewed at latest revision, 1 unresolved discussion. pkg/storage/node_liveness.go, line 276 at r1 (raw file): Previously, nvanbenschoten (Nathan VanBenschoten) wrote…
Good point, done. Comments from Reviewable |
Review status: 0 of 2 files reviewed at latest revision, 1 unresolved discussion, some commit checks failed. pkg/storage/node_liveness.go, line 276 at r2 (raw file):
Nit: put Comments from Reviewable |
4381f4e
to
5f19285
Compare
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.
5f19285
to
be1924e
Compare
Review status: 0 of 2 files reviewed at latest revision, 1 unresolved discussion, all commit checks successful. pkg/storage/node_liveness.go, line 276 at r2 (raw file): Previously, nvanbenschoten (Nathan VanBenschoten) wrote…
Done. Comments from Reviewable |
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, it now falls
back to reading the liveness record from the KV store.
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.