Manually starting NodeSync validation

Force NodeSync to repair specific segments. After a user validation is submitted, it takes precedence over normal NodeSync work. Normal work resumes automatically after the validation finishes.

For write-heavy workloads, where more than 20% of the operations are writes, you may notice CPU consumption overhead associated with NodeSync. If that’s the case for you environment, DataStax recommends using nodetool repair instead of enabling NodeSync. See nodetool repair.

This is an advanced tool. Usually, it is better to let NodeSync prioritize segments on its own.

  • Submitting user validations:

    nodesync validation submit keyspace_name.table_name
  • Listing user validations:

    nodesync validation list
  • Canceling user validations:

    nodesync validation cancel validation_id

Was this helpful?

Give Feedback

How can we improve the documentation?

© 2024 DataStax | Privacy policy | Terms of use

Apache, Apache Cassandra, Cassandra, Apache Tomcat, Tomcat, Apache Lucene, Apache Solr, Apache Hadoop, Hadoop, Apache Pulsar, Pulsar, 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. Kubernetes is the registered trademark of the Linux Foundation.

General Inquiries: +1 (650) 389-6000,