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

Unable to drop collection in admin database of sharded cluster

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.2.1, 4.3.1
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • ALL
    • v4.2
    • Hide
      ~$ mlaunch init --sharded 1 --replicaset --binarypath ./Downloads/mongodb-macos-x86_64-enterprise-4.3.0-824-g12c28db/bin
      ~$ mongo
      MongoDB shell version v4.2.0
      connecting to: mongodb://127.0.0.1:27017/?compressors=disabled&gssapiServiceName=mongodb
      Implicit session: session { "id" : UUID("b1e26e37-36d6-4f3f-a0d5-ff9c1abff5dd") }
      MongoDB server version: 4.3.0-824-g12c28db
      MongoDB Enterprise mongos> use admin
      switched to db admin
      MongoDB Enterprise mongos> db.test.insert({_id: 1})
      WriteResult({ "nInserted" : 1 })
      MongoDB Enterprise mongos> db.test.drop()
      true
      MongoDB Enterprise mongos> show collections
      system.keys
      system.version
      test
      MongoDB Enterprise mongos> db.test.find()
      { "_id" : 1 }
      
      Show
      ~$ mlaunch init --sharded 1 --replicaset --binarypath ./Downloads/mongodb-macos-x86_64-enterprise-4.3.0-824-g12c28db/bin ~$ mongo MongoDB shell version v4.2.0 connecting to: mongodb://127.0.0.1:27017/?compressors=disabled&gssapiServiceName=mongodb Implicit session: session { "id" : UUID("b1e26e37-36d6-4f3f-a0d5-ff9c1abff5dd") } MongoDB server version: 4.3.0-824-g12c28db MongoDB Enterprise mongos> use admin switched to db admin MongoDB Enterprise mongos> db.test.insert({_id: 1}) WriteResult({ "nInserted" : 1 }) MongoDB Enterprise mongos> db.test.drop() true MongoDB Enterprise mongos> show collections system.keys system.version test MongoDB Enterprise mongos> db.test.find() { "_id" : 1 }
    • Sharding 2019-08-26, Sharding 2019-09-09, Sharding 2019-09-23

      I'm unable to drop a collection in the admin database of a sharded cluster. This is affecting the ability to execute some driver tests which write to this database.

      The behavioral change occurred between v4.3.0-769-g81bb59c and v4.3.0-814-gb92fbdf.

            Assignee:
            esha.maharishi@mongodb.com Esha Maharishi (Inactive)
            Reporter:
            jeff.yemin@mongodb.com Jeffrey Yemin
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: