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

Mongos returns true when attempting to drop non-existent database

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Works as Designed
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      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?

            Assignee:
            esha.maharishi@mongodb.com Esha Maharishi (Inactive)
            Reporter:
            daniel.aprahamian@mongodb.com Daniel Aprahamian (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: