[
https://issues.apache.org/jira/browse/CASSANDRA-21493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18099863#comment-18099863
]
Caleb Rackliffe commented on CASSANDRA-21493:
---------------------------------------------
Just attached results for {{python-upgrade-dtests}} and
{{python-dtests-large}}...
Nothing there outside CASSANDRA-17339 and a couple upgrade failures that also
seem to be visible on
https://butler.cassandra.apache.org/#/ci/upstream/compare/Cassandra-trunk/trunk
I'll move to commit...
> 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
>
> Attachments: ci_summary-1.html, ci_summary-2.html,
> ci_summary-6.0.html, ci_summary.html, result_details.tar-1.gz,
> result_details.tar.gz
>
>
> A node whose decommission has failed can remain in the DECOMMISSION_FAILED
> even after resuming decommission. In this scenario, running `nodetool
> decommission` will resume the decommission and trigger streaming, while its
> state remains in DECOMMISSION_FAILED. This makes it difficult for operational
> tooling to distinguish between a terminal failure vs. and 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]
