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

dropDatabase should respect user provided writeConcern

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.0.0-rc1, 4.1.1
    • Storage
    • None
    • Fully Compatible
    • ALL
    • v4.0
    • 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
    • Storage NYC 2018-05-21, Storage NYC 2018-06-04
    • 0

    Description

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

      Attachments

        Issue Links

          Activity

            People

              louis.williams@mongodb.com Louis Williams
              shane.harvey@mongodb.com Shane Harvey
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: