Drop of a non-existing collection on mongod should have the same behavior as mongos

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • Execution Team 2023-02-20
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      In the standalone and non-sharded case, calling dropCollection a second time fails. However, in order to be idempotent (which we want for metadata commands that are run on the config server in a sharded cluster), we would need a second drop command to also succeed.

            Assignee:
            Dianna Hohensee (Inactive)
            Reporter:
            Kaitlin Mahar
            Votes:
            0 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated:
              Resolved: