-
Type: Bug
-
Resolution: Works as Designed
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
With the following command:
{ drop: 'a_collection_that_does_not_exist', writeConcern: { w: 'majority', wtimeout: 30000 } }
Sending the following command to a mongod (replicaset or standalone) results in an error ns not found. Sending the command to a mongos returns ok: 1.
Is this inconsistency expected?
- related to
-
SERVER-32365 Move the logic of the dropDatabase command into the new _configsvrDropDatabase command
- Closed