[SERVER-86323] Ensure maxKey is always logged in primary oplog for dbCheck Created: 06/Feb/24 Updated: 06/Feb/24 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Xuerui Fa | Assignee: | Backlog - Replication Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | pm-855-milestone-3 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Replication
|
| Participants: |
| Description |
|
If the user specifies no pre-defined range to check, we should make sure that both the extra and missing index key checks always log maxKey as the final end key of the last batch. This will ensure that we don't miss any entries on secondaries. We should have an explicit test for these as well. |