[
https://issues.apache.org/jira/browse/CASSANDRA-21493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Minal Kyada updated CASSANDRA-21493:
------------------------------------
Summary: Node can remain in DECOMMISSION_FAILED state even after resuming
decommission (was: Node remained in DECOMMISSION_FAILED even after resuming
decommission)
> Node can remain in DECOMMISSION_FAILED state 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
> Fix For: 6.x, 7.x
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
