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

Empty database when recreate in replicate set with priority

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 2.2.4
    • Component/s: Replication
    • Environment:
    • Windows
    • Hide

      Replica Set configuration:
      {
      "_id" : "rsaudit",
      "version" : 4,
      "members" : [

      { "_id" : 0, "host" : "LOG-MNG12:27017", "priority" : 10 }

      ,

      { "_id" : 1, "host" : "log-mng22:27017" }

      ,

      { "_id" : 2, "host" : "log-mng23:27018", "arbiterOnly" : true }

      ]
      }

      Stop MongoDB service, delete database folder and then restart the service again.

      Show
      Replica Set configuration: { "_id" : "rsaudit", "version" : 4, "members" : [ { "_id" : 0, "host" : "LOG-MNG12:27017", "priority" : 10 } , { "_id" : 1, "host" : "log-mng22:27017" } , { "_id" : 2, "host" : "log-mng23:27018", "arbiterOnly" : true } ] } Stop MongoDB service, delete database folder and then restart the service again.

      I tried to recreate a database on one node of the replica set (this node has more priority than others). I stopped the service and deleted the database folder. Then I started the service again but mongod have created an empty database and the node became primary to the replica set, meanwhile others nodes keeeped their database without problems.

            Assignee:
            Unassigned Unassigned
            Reporter:
            david.verdejo@logitravel.com David Verdejo
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: