-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Execution
-
Fully Compatible
-
Execution Team 2024-02-19, Execution Team 2024-03-04
If a collection has replicated record ids, dbHash can scan in record id order rather than _id order. dbHash currently scans in _id order. For recordIdReplicated:true collections, we can go in natural order, as we already do for clustered collections.
Additionally, we should include each recordId when computing the hash, to make sure that the recordIds are indeed replicated.
In this ticket we need to handle just dbHash, not dbCheck.
This will also help with SERVER-86167 because then our tests can rely on dbHash for correctness.
- depends on
-
SERVER-78348 Apply inserts on secondaries using record id
- Closed
- is depended on by
-
SERVER-86689 Create recordIdsReplicated:true jscore test that runs in all replica set / sharding scenarios
- Closed
- is duplicated by
-
SERVER-86212 Make dbHash be smart for recordIdReplicated:true collections
- Closed
- related to
-
SERVER-86902 Add flag to dbHash to go in recordId order / include recordIds
- Closed