shardCollection and movePrimary should not be allowed to run in parallel

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Gone away
    • Priority: Major - P3
    • None
    • Affects Version/s: 3.5.1
    • Component/s: Sharding
    • None
    • ALL
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      on the same parent database.

      The last phase of the movePrimary command is to drop collections on the shard that were not sharded before the movePrimary command started. So if the collection becomes sharded half way through, the movePrimary command can accidentally drop the collection.

            Assignee:
            Esha Maharishi (Inactive)
            Reporter:
            Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: