It looks like the dropDatabase command ignores write concern wtimeout on 3.7 replica sets. Is this intentional?
- is depended on by
-
TOOLS-2035 mongofiles_write_concern_mongos.js fails on server unstable
- Closed
- is related to
-
SERVER-34922 mongofiles sharded cluster write concern test regression in MongoDB 3.7
- Closed
-
SERVER-47194 dropDatabase command does not honor wtimeout on v3.6
- Closed
- related to
-
SERVER-33317 3.7 sharded clusters ignore create command write concern
- Closed
-
SERVER-40712 Clarify the behaviour of `db.dropDatabase` and the `dropDatabase` command
- Closed
-
SERVER-46668 createIndexes command does not honor wtimeout when replication is disabled on v4.5.0-24-gb801dec
- Closed
-
SERVER-53254 increase writeConcern timeout for dropDatabase in tests
- Closed