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

dropDatabase should respect user provided writeConcern

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.0.0-rc1, 4.1.1
    • Component/s: Storage
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.0
    • Steps To Reproduce:
      Hide

      1) disable replication on secondaries
      2) run dropDatabase command with writeConcern:

      {w:'majority', wtimeout:1}

      3) dropDatabase hangs (forever?) instead of raising a wtimeout error

      Show
      1) disable replication on secondaries 2) run dropDatabase command with writeConcern: {w:'majority', wtimeout:1} 3) dropDatabase hangs (forever?) instead of raising a wtimeout error
    • Sprint:
      Storage NYC 2018-05-21, Storage NYC 2018-06-04
    • Linked BF Score:
      20

      Description

      It looks like the dropDatabase command ignores write concern wtimeout on 3.7 replica sets. Is this intentional?

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              louis.williams Louis Williams
              Reporter:
              shane.harvey Shane Harvey
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: