Remove all secondary hosts from replica set (rs.remove(‘host:port’)), restart the mongo deamon without replSet parameter (editing /etc/mongo.conf) and the secondary hosts starts in standalone mode again. The Primary host is tricky one, because you can’t remove it from the replica set with rs.remove. Once you have only the primary node in the replica set, you … Read more
Note: Be sure to check the answer provided by arcseldon for an user friendly equivalent. You can use output of rs.status(). If secondary is synced and wasn’t created with slaveDelay option then optime and optimeDate of secondary should be equal or close (if there are current operations) to those of primary. In that case stateStr … Read more
Is there any problem/disadvantage with running Mongo as a 1-node replica set, assuming I don’t really need the replication, load balancing or any other scalable functionality? You don’t have high availability afforded by a proper replica set. Thus it’s not recommended for a production deployment. This is fine for development though. Note that a replica … Read more
Replica Set is the next generation of Replication Controller. Replication controller is kinda imperative, but replica sets try to be as declarative as possible. 1.The main difference between a Replica Set and a Replication Controller right now is the selector support. +————————————————–+—————————————————–+ | Replica Set | Replication Controller | +————————————————–+—————————————————–+ | Replica Set supports the … Read more