[SERVER-47194] dropDatabase command does not honor wtimeout on v3.6 Created: 30/Mar/20  Updated: 06/Dec/22  Resolved: 02/Apr/20

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 3.6.17
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Shane Harvey Assignee: Backlog - Storage Execution Team
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-34776 dropDatabase should respect user prov... Closed
Assigned Teams:
Storage Execution
Operating System: ALL
Participants:

 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

Generated at Thu Feb 08 05:13:32 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.