[
https://issues.apache.org/jira/browse/CASSANDRA-20655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ariel Weisberg updated CASSANDRA-20655:
---------------------------------------
Description:
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 all ranges, but this
isn't the most ergonomic behavior since in practice people end up using "-pr"
and then repair each node one by one. Since we don't have to support backwards
compatibility with Repair's parameters we should have begin and
finish-migration both default to the primary range.
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.
was:
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.
> 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
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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 all ranges, but
> this isn't the most ergonomic behavior since in practice people end up using
> "-pr" and then repair each node one by one. Since we don't have to support
> backwards compatibility with Repair's parameters we should have begin and
> finish-migration both default to the primary range.
> 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: [email protected]
For additional commands, e-mail: [email protected]
