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

db.dropDatabase is not erasing the database entry from the configdb config.collections

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Major - P3 Major - P3
    • None
    • 2.4.9
    • Sharding
    • None
    • ALL

    Description

      >create databases "test1" -"test10" activate sharding
      >create one collection "coll1" in each database + activate sharding (hashed shard key)
      >insert documents

      >drop databases

      >ceate databases "test1" -"test10"..
      >try activate sharding
      =>

      Command: { "shardCollection" : "test1.coll1" , "key" : { "_id" : "hashed"}}. Know error msg: already sharded

      config.collections
      {
        "_id" : "test1.coll1",
        "lastmod" : ISODate("1970-01-17T04:04:12.228Z"),
        "dropped" : true
      }

      in config.databases "test1"-"test10" is dropped.

      SERVER-2253

      Attachments

        Activity

          People

            thomas.rueckstiess@mongodb.com Thomas Rueckstiess
            Björn Bullerdieck Björn Bullerdieck [X]
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: