NodeSync Service
Monitor keeping keyspace and table replicas synchronized with the OpsCenter NodeSync Service for DSE versions 6.0 and later.
NodeSync automatically and continuously synchronizes replicas of designated keyspaces and tables of a cluster as a background process. The NodeSync Service is initially enabled by default in DSE version 6.0 and later but the keyspaces and tables that are actively monitored by the OpsCenter NodeSync Service must be enabled. Enable keyspaces and tables with a click of a button in the Settings area of NodeSync.
NodeSync metrics for alerts and dashboard graphs
NodeSync metrics are available to indicate progress on repaired data and objects (rows and range tombstones), validated data and objects, and processed pages details. Set up alerts and dashboard graphs based on NodeSync metrics pertinent to your production environment.
NodeSync Best Practice Rule
The NodeSync Best Practice Service rule checks that NodeSync is running on each node. The NodeSync Not Running rule in the Best Practice Service fails if the NodeSync Service is not running, unless the rule has been turned off.
For more details, see the Best Practice Service.
Tuning throughput for NodeSync
gc_grace period for a table, throughput must be adjusted by an operator or
administrator using the rate_in_kb parameter. Adjusting the throughput rate for
NodeSync can conveniently be set in a Lifecycle Manager Config Profile and the configuration
update pushed out by running a configuration job. See Configuring the NodeSync rate using LCM. For
information about manually configuring NodeSync, refer to the nodetool nodesyncservice.NodeSync Service versus Repair Service
Unlike incremental repairs in the Repair Service, the NodeSync Service does not build a Merkle tree for comparisons and stream differences for compaction. Rather, the NodeSync incrementally scans a token range, compares data a page at a time, and sends data over the standard write path.