Fix distributed locking on movePrimary

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Gone away
    • Priority: Major - P3
    • None
    • Affects Version/s: 3.5.8
    • Component/s: Sharding
    • None
    • ALL
    • Sharding 2017-07-10, Sharding 2017-07-31
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently, the movePrimary command takes a distlock identified by database name and command name. This ticket makes it take the database name distlock to avoid concurrency issues with other metadata commands.

            Assignee:
            Jessica Yu (Inactive)
            Reporter:
            Jessica Yu (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: