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

(DropDatabase + Sharding + Prefixed DB Name) = drops multiple collections

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Critical - P2 Critical - P2
    • None
    • 1.8.0
    • Sharding
    • None
    • Ubuntu 10.10
    • ALL

    Description

      See attached or Gist for script to reproduce. Run against an empty sharded test environment as it is dropping data unexpectedly.
      https://gist.github.com/882010

      ------
      Original report: http://groups.google.com/group/mongodb-user/browse_thread/thread/f3c0aee26fca75e9#
      ------

      The basic premise is simple, we have three databases with a "prefixed" name.
      db2 = db.getSisterDB('fred_sharded') // sharded
      db3 = db.getSisterDB('fred_sharded2') // also sharded
      db4 = db.getSisterDB('fred_shardednot') // not sharded

      If I drop db2, data from db3 also loses data:
      db2.runCommand(

      {dropDatabase:1}

      )

      db4 (unsharded) seems unaffected

      Attachments

        Activity

          People

            Unassigned Unassigned
            gatesvp Gaetan Voyer-Perrault
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: