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

CollectionCloner should handle QueryPlanKilled on collection drop

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.6.12, 4.0.7
    • Affects Version/s: 3.4.19, 3.6.10, 4.0.6
    • Component/s: Querying, Replication
    • Labels:
    • Fully Compatible
    • ALL
    • v4.0, v3.6, v3.4
    • Query 2019-02-25, Query 2019-03-11

      The CollectionCloner, used in the first phase of initial sync, has code to interpret error codes from the getMore command as indicative of a collection drop:


      In 4.0 and older branches, it handles OperationFailed and CursorNotFound. However, collection drops can result in a getMore returning QueryPlanKilled. This error code should be handled as well. This was fixed in 4.1.7 by SERVER-37451, but it still needs to be fixed in older branches. As part of moving ClientCursor ownership to the global cursor manager, SERVER-37451 changed the server's behavior such that collection drops result in QueryPlanKilled rather than CursorNotFound. This necessitated an immediate fix in master in order to ensure that initial sync remains resilient to collection drops. This ticket tracks the remaining backport work.

            david.storch@mongodb.com David Storch
            david.storch@mongodb.com David Storch
            0 Vote for this issue
            3 Start watching this issue