[
https://issues.apache.org/jira/browse/CASSANDRA-20281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17934660#comment-17934660
]
Jaydeepkumar Chovatia commented on CASSANDRA-20281:
---------------------------------------------------
Thanks, [~dcapwell], for pointing this out. Yeah, there are four ways to remove
a node. I have updated the description accordingly.
> Capability to run repair before replacing a node
> ------------------------------------------------
>
> Key: CASSANDRA-20281
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20281
> Project: Apache Cassandra
> Issue Type: Improvement
> Components: Consistency/Repair
> Reporter: Jaydeepkumar Chovatia
> Assignee: Jaydeepkumar Chovatia
> Priority: Normal
>
> It is vital to repair the token range of the node being replaced to avoid
> data loss as part of a node replacement.
> There is no better mechanism to repair a node before replacing it. As part of
> this ticket, we can discuss various ideas for extending the AutoRepair
> framework.
> There are four different ways to remove a node from the ring:
> # nodetool decommission
> # -Dcassandra.replace_address=<IP_of_dead_node>
> # nodetool assassinate
> # nodetool removenode
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
