Understanding all the Options for Replica-sets and Replication Patterns
summary
Explains concrete MongoDB replica set choices: clusters can have up to 50 members but only 7 voting members matter for elections, elections move to a term-based algorithm since 3.2 so failovers are faster, chaining reduces primary load, and ntpd-synced clocks avoid cluster bugs. Use hidden secondaries for offline backups and delayed secondary (seconds-based slaveDelay) as a hot standby to recover recent drops. Configure with rs.conf and rs.reconfig, set decimal priorities to control primaries, prefer writeConcern majority plus journaling, and use tags and maxStaleness for datacenter routing.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 0:18About Me
- 0:51Agenda
- 1:25Replication Features
- 3:44Other Replication Features
- 7:54Voting
- 12:51Delayed Secondaries
- 15:37Setting Priorities
- 18:29Write Concern
- 21:58Read Concern Parameters
- 22:36Read Preference
- 25:59Tags
- 27:23Housekeeping
related talks
37mBuilding MongoDB Replica
44mHow Raft consensus algorithm will make replication even better in MongoDB 3 2
24mMoving MongoDB to the Cloud: Strategies and points to consider
44mHow Raft consensus algorithm will make replication even better in MongoDB 3 2
47mDatabase Resiliency
32mA New Sharding Architecture for MongoDB
12mFault-Tolerant Replication with Pull-Based Consensus in MongoDB
30mHow to Automate, Monitor and Manage your MongoDB Servers