[
https://issues.apache.org/jira/browse/CASSANDRA-20655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17952280#comment-17952280
]
Ariel Weisberg commented on CASSANDRA-20655:
--------------------------------------------
Don't forget to update docs for `begin-migration` which currently point out
that the default with no arguments is to mark the entire ring as migrating.
> 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
> 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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
