Create collection on sharded cluster should not return NamespaceNotFound

XMLWordPrintableJSON

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

      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:
              [DO NOT USE] Backlog - Sharding EMEA
              Reporter:
              Tommaso Tocci
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: