Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-86323

Ensure minKey/maxKey is always logged in primary oplog for dbCheck

    • Type: Icon: Bug Bug
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Replication
    • Repl 2024-06-24, Repl 2024-07-08, Repl 2024-07-22

      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.

            Assignee:
            huayu.ouyang@mongodb.com Huayu Ouyang
            Reporter:
            xuerui.fa@mongodb.com Xuerui Fa
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: