[SERVER-78435] Scan in record id order for dbHash Created: 26/Jun/23 Updated: 05/Feb/24 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Gregory Noma | Assignee: | Haley Connelly |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Storage Execution
|
||||||||||||||||
| Sprint: | Execution Team 2024-02-19 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
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. |