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

shardCollection and movePrimary should not be allowed to run in parallel

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Gone away
    • Icon: Major - P3 Major - P3
    • None
    • 3.5.1
    • Sharding
    • None
    • ALL

    Description

      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.

      Attachments

        Activity

          People

            esha.maharishi@mongodb.com Esha Maharishi (Inactive)
            randolph@mongodb.com Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: