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

Sam Tunnicliffe updated CASSANDRA-21591:
----------------------------------------
    Status: Ready to Commit  (was: Review In Progress)

Sorry that this took way longer than it should have. I've rebased and re-run CI 
again, against these branches and attached the results. 

||Base Version||Branch||
|[6.0|https://github.com/beobal/cassandra/tree/samt/CASSANDRA-21591-6.0]|[trunk|https://github.com/beobal/cassandra/tree/samt/CASSANDRA-21591-trunk]

Everything looks as expected, so I've merged to 6.0 and trunk.
Thanks for the patch and for your patience! 


> Do not let a node be decommissioned if a CMS reconfiguration involving it is 
> in progress
> ----------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-21591
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-21591
>             Project: Apache Cassandra
>          Issue Type: Bug
>          Components: Transactional Cluster Metadata
>            Reporter: Nivy Kani
>            Assignee: Nivy Kani
>            Priority: Normal
>             Fix For: 6.0.x
>
>         Attachments: ci_summary 2.html, ci_summary.html, result_details 
> 2.tar.gz, result_details.tar.gz
>
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> Currently, `PrepareLeave` doesn't validate that the leaving node isn't part 
> of any in-progress CMS reconfiguration. This can cause the 
> ADVANCE_CMS_RECONFIGURATION step to fail.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to