Abstract out similar code between data consistency/extra index keys check and make error handling consistent

XMLWordPrintableJSON

    • Replication
    • Fully Compatible
    • v8.0, v7.0, v6.0
    • Repl 2024-02-19, Repl 2024-03-04, Repl 2024-03-18, Repl 2024-04-01, Repl 2024-05-13, Repl 2024-07-08, Repl 2024-07-22
    • 6
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      We should abstract out similar code between data consistency/extra index keys check, including error handling (for things like checking for stepdown, ErrorCodes::LockTimeout, adding handling for retryable errors in extra index keyds check)

      As part of this we should refactor the code to only check for the IndexNotFound/NamespaceNotFound/CommandNotSupportedOnView errors in one place/propogate it all up to one location, since right now in the extra index keys path we check for IndexNotFound in many locations.

      We should also make sure that all the IndexNotFound checks are correct (in dbcheck_extra_index_keys.js)

            Assignee:
            Xuerui Fa
            Reporter:
            Huayu Ouyang
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: