Is it possible to configure only one secondary and one primary in MongoDB Replication?
Mongodb – Replication members count limitation in MongoDB
master-slave-replicationmongodb
Related Question
- Unable to Configure MongoDB Replication Without Initial Sync
- MongoDB 3.2 – Understanding Simple Replication
- Mongodb – ADD new node Replication in MongoDB
- Mongodb – sharding and replication on mongodb
- MongoDB Replication with Two Machines – How to Solve
- Running an Arbiter on a Machine Hosting a Secondary Member in MongoDB 3.6
- Replication – MongoDB Replica Set Quorum Configuration and Network Partitioning Behavior
Best Answer
Yes! Of course!
But in the situation where you lose one of the nodes (primary or secondary), remaining node state will be secondary and you cannot insert/update/delete data. If you can add (one) arbiter to that replica set, your DB will keep working even you lose one node. Basically arbiter don't need many resources, smallest VPS node what you can find is enough. (512MB memory, 1 CPU, 10GB diskspace) OR you can even add that arbiter to that application machine what is connecting to that mongoDB.