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

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

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.1.12
    • Component/s: Storage
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Sprint:
      Storage NYC 2019-05-20

      Description

      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.

      Specifically:

      • 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, Danny 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.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              gregory.wlodarek Gregory Wlodarek
              Reporter:
              kaloian.manassiev Kaloian Manassiev
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: