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

Dropped database doesn't disappear due to replication

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Gone away
    • Affects Version/s: 1.6.4
    • Fix Version/s: None
    • Component/s: Replication
    • Labels:
    • Environment:
      Windows 2008 Datacenter edition
    • Operating System:
      Windows

      Description

      I'm calling db.dropDatabase() on a master of a master slave pair on windows, and it doesn't stay deleted. Console log:

      > db.getSisterDB('staging_KMI').dropDatabase()

      { "dropped" : "staging_KMI", "ok" : 1 }

      > show dbs
      STAGE_landroverKMI
      STAGE_landroverRSVP
      admin
      landroverKMI
      landroverRSVP
      local
      stageing_KMI
      staging_KMI

      > use staging_KMI
      > db.dropDatabase()

      { "dropped" : "staging_KMI", "ok" : 1 }

      > show dbs
      STAGE_landroverKMI
      STAGE_landroverRSVP
      admin
      landroverKMI
      landroverRSVP
      local
      stageing_KMI
      staging_KMI
      >

      Master/slave stuff

      Config on the master:

      "C:\Program Files\10gen\mongodb-win32-x86_64-1.6.4\bin\mongod.exe" --service --logpath c:\data\logs\mongo-master.log --logappend --master --bind_ip localhost

      Log on the master:
      Tue Jan 04 14:48:57 [conn201] dropDatabase staging_KMI

      Slave configuration:

      "C:\Program Files\10gen\mongodb-win32-x86_64-1.6.4\bin\mongod.exe" --service --logpath c:\data\logs\mongo-slave.log --logappend --dbpath c:\data\db_slave --slave --source localhost --port 27018 --bind_ip localhost

      Log on the slave:

      Tue Jan 04 14:48:55 [replslave] repl: applied 4 operations
      Tue Jan 04 14:48:55 [replslave] repl: end sync_pullOpLog syncedTo: Jan 04 14:48:55 4d233357:1
      Tue Jan 04 14:48:55 [replslave] repl: from host:localhost
      Tue Jan 04 14:48:55 [replslave] An earlier initial clone of 'staging_KMI' did not complete, now resyncing.
      Tue Jan 04 14:48:55 [replslave] resync: dropping database staging_KMI
      Tue Jan 04 14:48:55 [replslave] resync: cloning database staging_KMI to get an initial copy
      Tue Jan 04 14:48:56 [replslave] resync: done with initial clone for db: staging_KMI
      Tue Jan 04 14:48:57 [replslave] repl: applied 1 operations
      Tue Jan 04 14:48:57 [replslave] repl: end sync_pullOpLog syncedTo: Jan 04 14:48:57 4d233359:1
      Tue Jan 04 14:48:57 [replslave] repl: from host:localhost
      Tue Jan 04 14:48:57 [replslave] An earlier initial clone of 'staging_KMI' did not complete, now resyncing.
      Tue Jan 04 14:48:57 [replslave] resync: dropping database staging_KMI
      Tue Jan 04 14:48:57 [replslave] resync: cloning database staging_KMI to get an initial copy
      Tue Jan 04 14:48:57 [replslave] resync: done with initial clone for db: staging_KMI

        Attachments

          Issue Links

            Activity

              People

              Votes:
              13 Vote for this issue
              Watchers:
              20 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: