About node repair
Hyper-Converged Database (HCD) uses the node repair process to ensure that data in every replica is consistent with other replicas. Several different types of repair exist.
Over time, data in a replica can become inconsistent with other replicas due to the distributed nature of the database. Node repair corrects the inconsistencies so all nodes have the same and most up-to-date data. Node repair is an important part of regular maintenance for every HCD cluster. Use database settings or various HCD tools to configure each type of repair.
Read details about when to use and how to configure each repair type that HCD provides:
-
HCD provides the
nodetool repairtool to ensure data consistency across replicas. The tool compares the data across all replicas and then updates the data to the most recent version. Usenodetool repairas part of your regular maintenance routine.DataStax recommends stopping repair operations during topology changes.
Repairs running during a topology change are likely to throw an error when it involves moving ranges.
-
If a node becomes unable to receive a particular write, the write’s coordinator node preserves the data to be written as a set of hints. When the node comes back online, the coordinator hands off hints so that the node can catch up with the required writes.
-
During the read path, a query assembles data from several nodes. The coordinator node for the read compares the data from each replica node. If any replica node has outdated data, the coordinator node sends it the most recent version. The scope of this type of repair depends on the keyspace’s replication factor. During a read, the database collects only enough replica data to satisfy the replication factor, and only performs read repair on nodes that participate in that read operation.
