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

Create collection on sharded cluster should not return NamespaceNotFound

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Sharding EMEA
    • ALL

      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.

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

              Created:
              Updated:
              Resolved: