Skip to content

Fix operationMode stuck in DECOMMISSION_FAILED during resumed decommission#4920

Open
minal-kyada wants to merge 1 commit into
apache:trunkfrom
minal-kyada:node-decommission-fix
Open

Fix operationMode stuck in DECOMMISSION_FAILED during resumed decommission#4920
minal-kyada wants to merge 1 commit into
apache:trunkfrom
minal-kyada:node-decommission-fix

Conversation

@minal-kyada

Copy link
Copy Markdown
Contributor

Issue: When a node's decommission fails mid stream, it enters DECOMMISSION_FAILED mode. On the subsequent decommission --force resume, clearTransientMode() was never called, so operationMode() remained stuck as DECOMMISSION_FAILED throughout the resumed streaming, even though the node was actively leaving.

Fix: Added a clearTransientMode() call on the resume branch of decommission(), mirroring the same pattern already used by every other path that recovers a node from a failed state.

patch by @minal-kyada ; reviewed by @maedhroz and @beobal for CASSANDRA-21493

@minal-kyada
minal-kyada force-pushed the node-decommission-fix branch 2 times, most recently from a05b7f2 to c081555 Compare July 9, 2026 23:28
@minal-kyada
minal-kyada force-pushed the node-decommission-fix branch from c081555 to d5fbf23 Compare July 14, 2026 04:25
IInvokableInstance cmsNode = cluster.get(1);
IInvokableInstance leavingNode = cluster.get(2);

leavingNode.nodetoolResult("decommission", "--force").asserts().failure();

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ideally running nodetool decommission should be sufficient, right? --force flag required here?

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.

2 participants