How to reset MongoDB replica set settings

mongodb

I want to start over the configurations of replica, is it possible? How to reset it?

In group people saying to remove the database content, but are there any work around?

Best Answer

If you want to keep the data, but start outside a replica set, just restart the mongod process without the --replSet and on a different port. That will give you a standalone mongod.

To be completely sure that the replica set configuration is gone from the instance, make sure that the local.system.replset collection is empty.

Once that is done, and you are happy with your standalone instance, you can then restart with a different --replSet argument and go through the replica set configuration process again:

http://www.mongodb.org/display/DOCS/Replica+Set+Configuration

The other option, as you mention, is to remove all the data files and start completely from scratch.

Related Solutions

Is this a valid backup strategy for MongoDB

ReplicaSet will work in this scenario. However, I cannot tell if having two MongoDB instances at the same server is a good idea -- this depends on the server hardware/software and load.

To make sure your backup MongoDB node does not become master, set its priority parameter to 0, e.g.

rs.add({_id: 1, host: "localhost:<port>", priority: 0})

NOTE: if you cannot have downtime, you SHOULD have at least 2 primary MongoDB nodes in ReplicaSet, see article

Mongo replica set unable to import the example restaurant json

End the import just stops at 45%

It's probably fine and just building indexes. Or you could be running out of some system resource, or it could just be slow. Tail the logs for that mongod process for more information. Check your disk for free space, and check top or whatever system monitoring tools you have to see what resources are being used while the import appears to be stopped at 45%.

On the slave there is a database test created but if I try to do a find: db.restaurants.find();

I get back :
Error: error: { "$err" : "not master and slaveOk=false", "code" : 13435 }

You can't query data on a secondary without first telling your driver or the mongo shell that it's okay to do so. Run rs.slaveOk() first and then you can run your find() query.

Best Answer

Related Solutions

Is this a valid backup strategy for MongoDB

Mongo replica set unable to import the example restaurant json

Related Topic