-
Type:
New Feature
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Storage, Testing Infrastructure
-
None
-
Fully Compatible
-
TIG 2018-05-21, TIG 2018-06-04
-
0
-
3
This makes it possible to detect transient data inconsistency failures (e.g. related to timestamping differences between the primary and secondary of a replica set) that have been resolved by the time we've finished waiting for all operations to have replicated. This requires changing the "dbhash" command to call getMinimumVisibleSnapshot(), etc. as AutoGetCollectionForRead does currently.
- causes
-
SERVER-35253 `dbHash` can take locks in MODE_S while in a transaction
-
- Closed
-
- depends on
-
-
- Closed
-
- is depended on by
-
SERVER-34779 Check the dbhash periodically in a new version of the replica_sets_jscore_passthrough.yml test suite
-
- Closed
-
- related to
-
-
- Closed
-