[
https://issues.apache.org/jira/browse/CASSANDRA-20083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17941093#comment-17941093
]
Yuqi Yan commented on CASSANDRA-20083:
--------------------------------------
[~maxwellguo] Thank you for the pointer. I think our setup is slightly
different, that the node is bootstrapped with partial data when we replace some
unhealthy node in the ring that hasn't finished the rebuild. The new node is
already bootstrapped.
This nodetool option will be more handful as we just need to re-run the rebuild
nodetool on the new node so it'll be able to restart the rebuild process from 0
> Nodetool rebuild should have option to truncate range table
> -----------------------------------------------------------
>
> Key: CASSANDRA-20083
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20083
> Project: Apache Cassandra
> Issue Type: Improvement
> Components: Legacy/Streaming and Messaging
> Reporter: Yuqi Yan
> Assignee: Yuqi Yan
> Priority: Normal
> Labels: rebuilding
> Fix For: 5.x
>
>
> When rebuilding a new cluster, we sometimes replace a node from the new ring,
> and the new node was bootstrapped the data from nodes in the new cluster.
> It's obvious that other nodes in the new cluster doesn't have any data yet,
> but the new node is then marking the ranges available. Later the nodetool
> rebuild just finished immediately.
> It would be great to have an option to truncate this available ranges table
> in this nodetool so it'll just retry the rebuild.
> [PR|https://github.com/apache/cassandra/pull/3691/files]
--
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
