Tuning NodeSync validations

NodeSync tries to validate all tables within their respective deadlines, while respecting the configured rate limit. If a table is 10GB and has a deadline_target_sec=10 and the rate_in_kb is set to 1MB/sec, validation will not happen quickly enough. Configure the rate and deadlines realistically, take data sizes into account and adapt with data growth.

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 your environment, DataStax recommends using nodetool repair instead of enabling NodeSync. See nodetool repair.

NodeSync records warnings to the system.log if it detects any of the following conditions:

  • rate_in_kb is too low to validate all tables within their deadline, even under ideal circumstances.

  • rate_in_kb cannot be sustained by the node (too high for the node load/hardware).

Setting the NodeSync rate

Estimate NodeSync rate impacts and set rates.

Setting the NodeSync deadline

Adjust maximum time between NodeSync validations of the same data.

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, info@datastax.com