[FOLLOW UP QUESTION TO #8948]
Before decomm on-prim DC should repair be run all on on-prim DC nodes including newly built AWS DC or required to run repair only on new AWS DC nodes one at a time ?
Before decomm on-prim DC should repair be run all on on-prim DC nodes including newly built AWS DC or required to run repair only on new AWS DC nodes one at a time ?
The general recommendation is to regularly run repairs against your cluster regardless of topology changes. If you know that replicas are not consistent or you haven't been running repairs regularly, repair the existing nodes in the cluster before adding a new DC.
Running repair on the newly added nodes is not necessary immediately after they were added because they should be consistent with other replicas provided you followed the general recommendation above.
The standard procedure before decommissioning a DC is to run a full repair to make sure that replicas in all DCs are consistent before the DC is removed. For details, see Decommissioning a datacenter. Cheers!
5 People are following this question.
OpsCenter reports "Cannot run anti-entropy repair on tables with NodeSync enabled"
Repair kills the performance of the cluster
Getting "RuntimeException: Could not create snapshot" when running repairs
Can I enable nodesync and run OpsCenter repairs continuously?
Can we ALTER TABLE and disable NodeSync service and run nodetool repair?
DataStax Enterprise is powered by the best distribution of Apache Cassandra ™
© 2023 DataStax, Titan, and TitanDB are registered trademarks of DataStax, Inc. and its subsidiaries in the United States and/or other countries.
Apache, Apache Cassandra, Cassandra, Apache Tomcat, Tomcat, Apache Lucene, Lucene, Apache Solr, Apache Hadoop, Hadoop, Apache Spark, Spark, Apache TinkerPop, TinkerPop, Apache Kafka and Kafka are either registered trademarks or trademarks of the Apache Software Foundation or its subsidiaries in Canada, the United States and/or other countries.
Privacy Policy Terms of Use