[SERVER-86212] Make dbHash be smart for recordIdReplicated:true collections Created: 05/Feb/24 Updated: 05/Feb/24 Resolved: 05/Feb/24 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Vishnu Kaushik | Assignee: | Haley Connelly |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| 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. |