shardCollection can create shard index in the wrong shard

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: 3.3.12
    • Component/s: Sharding
    • None
    • ALL
    • 0
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      After a movePrimary, if a mongos that is not aware of it receives a shardCollection command on an empty collection, it can create the shard key index on the old primary shard of the database.

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

              Created:
              Updated:
              Resolved: