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

Create collection on sharded cluster should not return NamespaceNotFound

    XMLWordPrintableJSON

Details

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

    Description

      Consider the following flow of execution:

      1. mongos send a createColellection and receive a NamespaceExists error from the db primary shard
      2. the collection is dropped or renamed
      3. mongos calls checkCollectionOption and throws NamespaceNotFound since the collection doesn't exist anymore.

      Attachments

        Activity

          People

            backlog-server-sharding-emea [DO NOT USE] Backlog - Sharding EMEA
            tommaso.tocci@mongodb.com Tommaso Tocci
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: