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

Mongos returns true when attempting to drop non-existent database

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Works as Designed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      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?

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                Created:
                Updated:
                Resolved: