Self-Managed Replica Set Deployment Tutorials
MongoDB 5.0 is end of life as of October 2024. This version of the documentation is no longer
supported. To upgrade your 5.0 deployment, see the MongoDB 6.0 upgrade procedures.
The following tutorials provide information on deploying replica sets.
- Deploy a Self-Managed Replica Set
- Configure a three-member replica set for production systems.
- Deploy a Self-Managed Replica Set for Testing and Development
- Configure a three-member replica set for either development or testing systems.
- Deploy a Geographically Redundant Self-Managed Replica Set
- Create a geographically redundant replica set to protect against location-centered availability limitations (e.g. network and power interruptions).
- Add an Arbiter to a Self-Managed Replica Set
- Add an arbiter to give a replica set an odd number of voting members to prevent election ties.
- Convert a Standalone Self-Managed mongod to a Replica Set
- Convert an existing standalone
mongod
instance into a three-member replica set. - Add Members to a Self-Managed Replica Set
- Add a new member to an existing replica set.
- Remove Members from a Self-Managed Replica Set
- Remove a member from a replica set.
- Replace a Self-Managed Replica Set Member
- Update the replica set configuration when the hostname of a
member's corresponding
mongod
instance has changed.