dropDatabase command does not honor wtimeout on v3.6

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: 3.6.17
    • Component/s: None
    • None
    • Storage Execution
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Note: I believe this is the same bug as SERVER-34776 but on the v3.6 branch.

      The dropDatabase command does not honor wtimeout on v3.6. To reproduce:

      1. start a 3 node replica set with 3.6.17
      2. disable replication on secondaries: db.adminCommand({"configureFailPoint": "stopReplProducer", "mode": "alwaysOn"})
      3. run dropDatabase command with writeConcern:{w:3, wtimeout:1}
      4. dropDatabase hangs (forever?) instead of raising a wtimeout error

            Assignee:
            [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            Shane Harvey
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: