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

remove backwards compatible distlock from sharding catalog commands

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.7.3
    • Affects Version/s: 3.7.2
    • Component/s: Sharding
    • None
    • Fully Compatible
    • Sharding 2018-03-26

      The backwards compatible distlock was a distlock taken by sharding catalog commands on a database's name, plus "-movePrimary."

      It was taken by the sharding catalog commands in v3.6, because prior to v3.6, movePrimary had a bug that it took the database distlock with this "-movePrimary" suffix, rather than just the database's name.

      Now that we don't need to support backwards compatibility with <v3.6, we can remove the places where we take this backwards compatible distlock.

            Assignee:
            esha.maharishi@mongodb.com Esha Maharishi (Inactive)
            Reporter:
            esha.maharishi@mongodb.com Esha Maharishi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: