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

createCollection on mongos can create an unreachable collection if movePrimary has been called

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major - P3 Major - P3
    • None
    • 3.5.10
    • Sharding
    • None
    • Sharding
    • ALL

    Description

      createCollection on mongos does not check for the collection's existence in the cluster; it simply forwards the create command to (what it believes is) the database's primary shard.

      If movePrimary has been called from another mongos, this mongos will cause the collection to be created on the wrong (old primary) shard, leaving it unreachable.

      I believe once SERVER-30375 is done, this means we will be unable to migrate chunks for this collection onto this shard until the unreachable collection is manually deleted directly from the shard.

      Attachments

        Activity

          People

            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            esha.maharishi@mongodb.com Esha Maharishi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: