[jira] [Commented] (CASSANDRA-20281) Capability to run repair before replacing a node

["Jaydeepkumar Chovatia (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-20281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17934316#comment-17934316 ] 

Jaydeepkumar Chovatia commented on CASSANDRA-20281:
---------------------------------------------------

Here is a one-pager design for this ticket [https://docs.google.com/document/d/1SZIQPbIWNDsbWnIk5N5tyQCQzJ4ypwuhH-t5dO5WeZs/edit?tab=t.0]

> 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 two ways to remove a node from the ring:
>  # nodetool decommission: AutoRepair framework already has an option to force any live node to trigger repair, so we can leverage that readymade
>  # -Dcassandra.replace_address=<IP_of_dead_node>: Currently, the framework does not proxy repair on behalf of another node. It needs to be extended. 
>  



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