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

dropDatabase command does not honor wtimeout on v3.6

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Won't Fix
    • 3.6.17
    • None
    • None
    • None
    • Storage Execution
    • ALL

    Description

      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

      Attachments

        Issue Links

          Activity

            People

              backlog-server-execution Backlog - Storage Execution Team
              shane.harvey@mongodb.com Shane Harvey
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: