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

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

XMLWordPrintableJSON

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

      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@mongodb.com Dianna Hohensee (Inactive)
            Reporter:
            kaitlin.mahar@mongodb.com Kaitlin Mahar
            Votes:
            0 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated:
              Resolved: