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

Investigate optimizing dbcheck case where skipLookupForExtraKeys is true, if we can avoid doing two index walks

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Replication

      Right now we do one index walk for batching + reverse lookup, and one for hashing. If we skipLookupForExtraKeys, then we still need to do the first index walk for batching and then another one for hashing. We should investigate refactoring/optimizing this and see if we can just do one. This would mean we need to move/add logic for checking batch limits into the hasher. We should wait until after SERVER-80682 which changes the way we do batch limits for extra keys check

            Assignee:
            backlog-server-repl [DO NOT USE] Backlog - Replication Team
            Reporter:
            huayu.ouyang@mongodb.com Huayu Ouyang
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: