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
See nodesync validation.