Details
-
Task
-
Resolution: Duplicate
-
Major - P3
-
None
-
None
-
None
-
None
Description
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.
Attachments
Issue Links
- duplicates
-
SERVER-78435 Scan in record id order for dbHash
-
- Open
-