Read Repair: repair during read path
When a read query encounters inconsistent results at a consistency level greater than ONE or LOCAL_ONE, Hyper-Converged Database (HCD) initiates a read repair.
Such read repairs run in the foreground and block application operations until the repair process is complete.
|
Read queries with a consistency level of |
In more detail:
-
The coordinator node asks one replica for data and the others for a digest of their data.
-
If there is a mismatch in the data returned to the coordinator from the replicas, a read is requested from all replicas involved in the query (dictated by the consistency level) and the results are merged.
-
If a single replica doesn’t have all of the latest data for each column, a new record is assembled by mixing and matching columns from different replicas.
-
After determining the latest version, the record is written back to only the replicas involved in the request.
For example, in the case of a LOCAL_QUORUM read with a replication factor of three, two replicas are queried, so only those two replicas are repaired.
|
Read repair does not propagate expired tombstones, nor does it consider expired tombstones when actually repairing data.
That means that if there is tombstoned data that has not been propagated to all replica nodes before |
