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

Clarify the behaviour of `db.dropDatabase` and the `dropDatabase` command

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.1.12, 4.0.27
    • Affects Version/s: None
    • Component/s: Storage
    • Labels:
    • Fully Compatible
    • ALL
    • v4.0
    • Storage NYC 2019-05-20
    • 0

      The drop database command and shell helper are both documented as accepting write concern, but reading through the code and testing them seems to disagree with the documentation.


      • From the shell code it looks like db.dropDatabase does not allow any parameters. So how does one specify majority write concern through the shell helper?
      • Executing the dropDatabase command directly, without passing write concern seems to always result in a w:majority behaviour. In particular, daniel.hatcher performed these repro steps: "3 member replica set, fyncLocked 2 of the members, command hung on primary".

      I am filing this ticket to request clarification on the behaviour of the dropDatabase command and shell helper and to have the documentation updated.

            gregory.wlodarek@mongodb.com Gregory Wlodarek
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            0 Vote for this issue
            10 Start watching this issue