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

Make the sharded cluster's 'create' command behave the same as replica set

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • Sharding EMEA
    • ALL
    • Sharding EMEA 2021-11-29, Sharding EMEA 2021-12-13, Sharding EMEA 2021-12-27
    • 11
    • 3

      When a createCollection command is forwarded from the router to the database primary, it is possible to get a NamespaceExists error in case the collection already exists. When this happens, a listCollection command is issued in order to decide whether to return or not an error to the client (fail in case the collection exists with different options).

      However, there is no guarantee that a collection does not get dropped before the call to listCollection. In case this happens, currently a "cannot find ns" error message is returned, that is very misleading considering that the command should create the namespace.

            Assignee:
            backlog-server-sharding-emea [DO NOT USE] Backlog - Sharding EMEA
            Reporter:
            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            Votes:
            0 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated:
              Resolved: