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

investigate if $out, insert and create can return LockBusy instead of MovePrimaryInProgress for unsplittable collections

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Works as Designed
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing
    • ALL

      After SERVER-81190 any implicit collection creation will happen within the CreateCollectonCoordinator. 

      This causes the shardsvrCreateCollection (and therefore the caller) to fail with "LockBusy" in case a concurrent operation is in progress. 

      Specifically for the movePrimary, a special error "movePrimaryInProgress" is thrown for this case by specific operation such as createIndex.

      Insert, $out and "create" used to return movePrimaryInProgress and now return LockBusy.

      The goal of this ticket is to investigate whether is ok to now return LockBusy or instead movePrimaryInProgress should be enforced for back-compatibility

            Assignee:
            backlog-server-catalog-and-routing [DO NOT USE] Backlog - Catalog and Routing
            Reporter:
            enrico.golfieri@mongodb.com Enrico Golfieri
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: