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:
- start a 3 node replica set with 3.6.17
- disable replication on secondaries: db.adminCommand({"configureFailPoint": "stopReplProducer", "mode": "alwaysOn"})
- run dropDatabase command with writeConcern:{w:3, wtimeout:1}
- dropDatabase hangs (forever?) instead of raising a wtimeout error
Attachments
Issue Links
- related to
-
-
- Closed
-