Mongo replica set to single server

mongodb

I have a mongodb replica set and want to move it to a single server setup

Is it just as simple as doing a rs.remove() to the other 2 nodes?

Best Answer

On the current primary node of the replica set, you may issue the rs.remove() for those nodes, and thereby stopping replication attempts to them.

You will probably have to shut down the server that you want to run in single mode, and start it up again without the --replSet <name> option (or whatever it might be set to in your config file), as this will start the server in single mode, and not try to replicate to any other nodes.

Related Solutions

Can’t config replica set using MongoDB 3

Found the solution - It was permission issue.

In MongoDB configuration file, I had to turn off authentication mode or create a shared key between all nodes using this guide:

https://docs.mongodb.com/manual/tutorial/deploy-replica-set-with-keyfile-access-control/#deploy-repl-set-with-auth

This was the reason my servers couldn't communicate each other.

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

Can’t config replica set using MongoDB 3

Mongo replica set unable to import the example restaurant json

Related Topic