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

CollectionCloner should ignore NamespaceNotFound errors

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Replication
    • Operating System:
      ALL
    • Epic Link:
    • Case:
    • Linked BF Score:
      68

      Description

      If a collection is dropped on the sync source after we call listIndexes but before we start fetching, we will get a NamespaceNotFound error. We should ignore it rather than failing initial sync.

        Attachments

          Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. SERVER-31267 CollectionCloner fails if collection is dropped between getMore calls

          • Major - P3 - Major loss of function.
          • Closed
          is related to

          Task - A task that needs to be done. SERVER-33644 getMissingDoc in initial sync needs to be resilient to NamespaceNotFound

          • Major - P3 - Major loss of function.
          • Closed

            Activity

              People

              Assignee:
              backlog-server-repl Backlog - Replication Team
              Reporter:
              judah.schvimer Judah Schvimer
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: