[jira] [Updated] (CASSANDRA-19972) Nodetool cms reconfigure reports success when the operation fails due to streaming issues

["Sam Tunnicliffe (Jira)" <ji...@apache.org>]

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

Sam Tunnicliffe updated CASSANDRA-19972:
----------------------------------------
     Bug Category: Parent values: Correctness(12982)Level 1 values: Transient Incorrect Response(12987)
       Complexity: Normal
    Discovered By: DTest
    Fix Version/s: 5.x
         Severity: Normal
           Status: Open  (was: Triage Needed)

> Nodetool cms reconfigure reports success when the operation fails due to streaming issues
> -----------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-19972
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-19972
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Transactional Cluster Metadata
>            Reporter: Sam Tunnicliffe
>            Assignee: Sam Tunnicliffe
>            Priority: Normal
>             Fix For: 5.x
>
>
> If streaming fails during CMS reconfiguration, the operation enters a {{blocked}} state. The operation will still be pending and resumable by an operator & the KPI that indicates the CMS is pending/due reconfiguration will correctly indicate the state. However, the nodetool command itself exits with a success status which is especially problematic in tests. 
> This is easy to repro in an in-jvm dtest by attempting to a CMS reconfiguration without enabling the {{NETWORK}} feature on the cluster.



--
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