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

CollectionCloner fails when a collection is dropped and re-created between getMores

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Gone away
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Replication
    • Labels:
    • Operating System:
      ALL

      Description

      If a collection is dropped then immediately re-created on the primary while another node is doing an initial sync of that collection, the initial sync will fail with a CursorNotFoundError

      This is because when a collection is dropped, we delete the cursors completely, so we don't know why the cursor was killed.

      Possible fixes:

      Include uuid of collection in cursor objects; check existence of uuid (instead of or in addition to namespace) to return a CollectionDropped error.

      Keep killed cursors around for some length of time (or until the cursor is used), marked to say they were killed because the collection was dropped.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              backlog-server-repl Backlog - Replication Team
              Reporter:
              matthew.russotto Matthew Russotto
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: