You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Alan Wang (Jira)" <ji...@apache.org> on 2026/03/19 21:22:00 UTC

[jira] [Assigned] (CASSANDRA-20655) consensus_admin begin-migration should default to primary range

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

Alan Wang reassigned CASSANDRA-20655:
-------------------------------------

    Assignee: Alan Wang

> consensus_admin begin-migration should default to primary range
> ---------------------------------------------------------------
>
>                 Key: CASSANDRA-20655
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-20655
>             Project: Apache Cassandra
>          Issue Type: Bug
>            Reporter: Ariel Weisberg
>            Assignee: Alan Wang
>            Priority: Normal
>
> Currently it marks the entire ring as migrating and this doesn’t match what `finish-migration` does which is just migrate the primary range for the node that nodetool is run against. Repair defaults to repairing a primary range so the way to repair a cluster is to run repair on each node which is straightforward to explain/understand so we should make migration consistent with that.
> If people want to mark the entire ring as migrating there is a separate config option to do that automatically when the table is altered.



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