The checkMetadataConsistency shard-key index check was disabled on secondaries in SERVER-130595.
The check could report false positives on secondaries because it did not read the indexes and the CSR at a consistent point in time. Specifically, secondaries pin a snapshot timestamp for disk reads, but the CSR was not read using that same timestamp.
- depends on
-
SERVER-130595 MoveRangeCoordinator should use the incremental authoritative commit
-
- Closed
-
- is related to
-
SERVER-130787 checkMetadataConsistency on secondary can report false positive due to CSR being newer than durable read timestamp
-
- Closed
-
-
-
- Closed
-