[
https://issues.apache.org/jira/browse/CASSANDRA-20582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17946726#comment-17946726
]
Andy Tolbert commented on CASSANDRA-20582:
------------------------------------------
A few considerations that we should discuss whether are in scope:
* When updating the keyspace replication to include a new DC, running rebuild
is more effective than repair. How should auto repair react in such a case?
* We decreasing RF, running a cleanup is usually a good idea (although not
strictly required). cleanups are probably not something we'd want to run
without the user initiating it themselves.
* Some RF changes can cause you to violate consistency (depending on CLs being
used and how much you change the RF); not sure it would be in scope to protect
against but worth discussing.
> Repair automatically when keyspace replication factor changes
> -------------------------------------------------------------
>
> Key: CASSANDRA-20582
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20582
> Project: Apache Cassandra
> Issue Type: Task
> Components: Consistency/Repair
> Reporter: Jaydeepkumar Chovatia
> Priority: Normal
>
> Whenever Keyspace replication factor changes, we need to run repair to ensure
> data consistency. As part of this ticket, we will extend the AutoRepair
> framework to take care of this flow.
--
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
