You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Minal Kyada (Jira)" <ji...@apache.org> on 2026/07/09 20:55:00 UTC

[jira] [Updated] (CASSANDRA-21493) Node remained in DECOMMISSION_FAILED even after resuming decommission

     [ https://issues.apache.org/jira/browse/CASSANDRA-21493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Minal Kyada updated CASSANDRA-21493:
------------------------------------
    Reviewers: Caleb Rackliffe, Marcus Eriksson

> Node remained in DECOMMISSION_FAILED even after resuming decommission
> ---------------------------------------------------------------------
>
>                 Key: CASSANDRA-21493
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-21493
>             Project: Apache Cassandra
>          Issue Type: Bug
>          Components: Transactional Cluster Metadata
>            Reporter: Minal Kyada
>            Assignee: Minal Kyada
>            Priority: Normal
>
> A node decommission got failed and it went into DECOMMISSION_FAILED state. Ran nodetool decommission again for that node. Streaming started after that, but operation mode remained in DECOMMISSION_FAILED. It makes it difficult for tooling to detect decommissioned failed instance vs in-progress decommission.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org