You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sam Tunnicliffe (Jira)" <ji...@apache.org> on 2025/11/17 19:24:00 UTC
[jira] [Commented] (CASSANDRA-21006) PrepareJoin should be rejected if tokens are already assigned
[ https://issues.apache.org/jira/browse/CASSANDRA-21006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18038960#comment-18038960 ]
Sam Tunnicliffe commented on CASSANDRA-21006:
---------------------------------------------
CI results to follow
> PrepareJoin should be rejected if tokens are already assigned
> -------------------------------------------------------------
>
> Key: CASSANDRA-21006
> URL: https://issues.apache.org/jira/browse/CASSANDRA-21006
> Project: Apache Cassandra
> Issue Type: Improvement
> Components: Transactional Cluster Metadata
> Reporter: Sam Tunnicliffe
> Assignee: Sam Tunnicliffe
> Priority: Normal
> Fix For: 6.x
>
>
> Currently a {{PrepareJoin}} transform can succeed if the tokens to be assigned to the joining peer already belong to another node. This is not especially unsafe as the join operation itself will be rejected at the {{StartJoin}} phase, but it is suboptimal as the planned operation has to then be cancelled in order to unlock the ranges.
--
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