Gracefully handle failing to acquire the distributed lock in a sharded cluster

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Won't Fix
    • Priority: Minor - P4
    • None
    • Affects Version/s: 3.1.2
    • Component/s: mongorestore
    • None

      "Failed: restore error: jstests_tool_dumprestore_sharded.cappedColl: error creating collection jstests_tool_dumprestore_sharded.cappedColl: error running create command: Lock for createDatabase is taken."
      

      When restoring multiple collections in parallel, each client will queue up on the distributed lock to create the database in the sharded cluster. The timeout was increased from 1 second to 5 seconds as part of SERVER-18504, but it would nice for the tools to still have retry logic for attempting to create the collection again, or alternatively create the collections using a single client and avoid this issue.

              Assignee:
              Unassigned
              Reporter:
              Max Hirschhorn
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: