Operational Defect Database
BugZero found this defect 103 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
MongoDB | 2568958
Ensure minKey/maxKey is always logged in primary oplog for dbCheck
Last update date:
3/15/2024
Affected products:
MongoDB Server
Affected releases:
No affected releases provided.
Fixed releases:
No fixed releases provided.
Description:
Info
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 minKey as the startKey of the first batch. In addition, we must log the 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.
Top User Comments
Steps to Reproduce
