movePrimary should take the same (dist)lock as shardCollection to ensure UUID consistency

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 3.5.13
    • Affects Version/s: 3.5.10
    • Component/s: Sharding
    • None
    • Minor Change
    • ALL
    • Sharding 2017-07-31, Sharding 2017-08-21, Sharding 2017-09-11
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      movePrimary changes the collection's UUID, since it clones the collection to the new primary shard.

      if shardCollection is called concurrently, it may persist the original collection's UUID on the config server, leaving the UUIDs inconsistent between the cloned collection and the config server.

              Assignee:
              Hugh Han (Inactive)
              Reporter:
              Esha Maharishi (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: