@Milos.Tepavcevic_175445 NodeSync's biggest advantage is that you no longer need to run repairs manually or use tools to run repairs because it is constantly running in the background. It is designed to be more efficient by repairing small ranges and keeping track of which ranges have been synced so they don't get repaired again until the next cycle. It also keeps a record of whether the sync was successful so a failed task gets rescheduled. Cheers!
6 People are following this question.
nodesync working abnormally after dropping all keyspaces
Why am I seeing unexpected behavior like lots of read-repairs and hint handoffs?
Unexpected error while recording NodeSync validation
Do we need to run nodesync on all nodes in the cluster?
Does NodeSync do a scheduled sub-range repair in the background?
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