[
https://issues.apache.org/jira/browse/CASSANDRA-21222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson updated CASSANDRA-21222:
----------------------------------------
Fix Version/s: 6.0-alpha2
7.0
(was: 6.x)
Source Control Link:
https://github.com/apache/cassandra/commit/af5eed2a3277b747a1a4a2b7bb18dce39fb167d5
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> Handle lost response when committing PrepareMove and PrepareLeave
> -----------------------------------------------------------------
>
> Key: CASSANDRA-21222
> URL: https://issues.apache.org/jira/browse/CASSANDRA-21222
> Project: Apache Cassandra
> Issue Type: Improvement
> Components: Transactional Cluster Metadata
> Reporter: Marcus Eriksson
> Assignee: Marcus Eriksson
> Priority: Normal
> Fix For: 6.0-alpha2, 7.0
>
>
> When starting a move or a decommission we commit the corresponding
> {{PrepareX}} transformation to set up the MultiStepOperation - if the
> response to the Prepare commit is lost we just fail the nodetool command and
> never resume the MSO. Instead we should mark the move/decom as failed to
> allow the operator to resume or abort it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
