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

dropDatabase should respect user provided writeConcern

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.0.0-rc1, 4.1.1
    • Affects Version/s: None
    • Component/s: 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

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

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

              Created:
              Updated:
              Resolved: