Exploring the replication in MongoDB
0 likes432 views
Redundancy and high availability are the basis for all production deployments. With MongoDB this can be achieved by deploying replica set. In this slides we are exploring how the replication works with MongoDB, why you should use replication, what are the features and go over different deployment use cases. At the end we are comparing some features with MySQL replication and what are the differences between the two
![Build indexes
members[n].buildIndexes : false
• Can be only set when adding a member to a replica set
• Can not be changed on running node
• Indexes on _id will still exist
• Priority must be set to 0, recommended as hidden:true
Useful when
• Node is used for backups using mongodump
• Node does not receive queries from clients
• Adding indexes and maintenance overburdens the host
system](https://image.slidesharecdn.com/perconalive-exploringthereplicationinmongodb-161019093726/85/Exploring-the-replication-in-MongoDB-21-320.jpg)
![Write concern
Write concern specification
{ w: <value>, j: <boolean>, wtimeout: <number> }
• w - number
– Option for “majority”
• j - write operation has been written to the journal
• wtimeout - time limit, in milliseconds, for the write concern
Replica set get write concern setting
rsTest:PRIMARY> rs.conf().settings['getLastErrorDefaults']
{ "w" : 1, "wtimeout" : 0 }](https://image.slidesharecdn.com/perconalive-exploringthereplicationinmongodb-161019093726/85/Exploring-the-replication-in-MongoDB-24-320.jpg)
Ad
More Related Content
What's hot (20)
Similar to Exploring the replication in MongoDB (20)
Ad
Recently uploaded (20)
Ad
Exploring the replication in MongoDB
- 1. Exploring the replication in MongoDB Date: Oct-4-2016
- 2. About us Lead Database Consultant @Pythian OSDB managed services since 2014 https://mk.linkedin.com/in/igorle @igorLE Database Consultant @Pythian OSDB managed services since 2014 https://tr.linkedin.com/in/okanbuyukyilmaz
- 3. Overview • Why Replication, replication definition • How replication works, replication concepts • Replica set features, deployment architectures • Replica set configuration options • Key metrics to monitor when running replica set • MySQL replication compared to MongoDB replication • Galera replication compared to MongoDB replication
- 4. Definition • Group of mongod processes that maintain the same data set • Redundancy and high availability • Increased read capacity
- 5. Replication concept • Write operations go to the Primary node • All changes are recorded into operations log - oplog • Asynchronous replication • Secondaries replicate the Primary oplog • Secondary can use sync source other Secondary • One Arbiter node per replica set • Automatic failover. Any node can become Primary
- 7. Replica set oplog • Special capped collection that keeps a rolling record of all operations that modify the data stored in the databases • Idempotent • Default oplog size For Unix and Windows systems Storage Engine Default Oplog Size Lower Bound Upper Bound In-memory 5% of physical memory 50MB 50GB WiredTiger 5% of free disk space 990MB 50GB MMAPv1 5% of free disk space 990MB 50GB
- 8. Replica set oplog ● Workloads that might require larger oplog size ○ updates to multiple documents at once ○ Deletions equal the same amount of data as inserts ○ Significant number of in-place updates ● Oplog status ○ rs.printReplicationInfo() - on a Secondary node ○ rs.printSlaveReplicationInfo() - on a Primary node ○ db.getReplicationInfo() - by using the local database
- 9. Deployment MongoDB configuration file: /etc/mongod.conf Before MongoDB 3.0 replSet=MyRepl oplogSize=4096MB YAML format since 3.0 replication: replSetName: MyRepl oplogSizeMB: 4096
- 10. Deployment • 3 node replica set Node1 Node2 Node3
- 11. Deployment Node1 /usr/bin/mongod -f mongod.conf > rs.initialize() Node2 Node3 Primary
- 14. Replica set maintenance • rs.status() • rs.conf() • rs.reconfig() • rs.remove() • rs.stepDown() • rs.freeze() • rs.isMaster() • rs.syncFrom() • rs.printReplicationInfo() • rs.printSlaveReplicationInfo()
- 15. Configuration options • 50 members per replica set (7 voting members) • Arbiter node • Hidden node • Priority 0 node • Delayed node • Build indexes • Fault tolerance • Write concern • Read preference
- 16. Configuration options rsTest:PRIMARY> rs.conf() { "_id" : "rsTest", "version" : 2, "members" : [ { "_id" : 0, "host" : "node1:27017", "arbiterOnly" : false, "buildIndexes" : true, "hidden" : false, "priority" : 1, "tags" : {"dc" : "apac"}, "slaveDelay" : 0, "votes" : 1 },
- 17. Arbiter node • Votes in elections • Does not hold copy of data { "_id" : <num> "host" : <hostname:port>, "arbiterOnly" : true, …. } hidden : true
- 18. Hidden node • Never becomes primary • Not visible to application • Use cases ○ reporting ○ backups { "_id" : <num> "host" : <hostname:port>, "priority" : 0, "hidden" : true } hidden : true
- 19. Priority 0 node Priority - floating point (i.e. decimal) number between 0 and 1000 • Hidden members and Delayed slave with priority 0 by default • Never becomes primary • Visible to application { "_id" : <num> "host" : <hostname:port>, "priority" : 0 }
- 20. Delayed node • must be priority 0 member • should be hidden member (not mandatory) • has votes 1 by default • considerations (oplog size) • mainly used for backups { "_id" : <num>, "host" : <hostname:port>, "priority" : 0, "slaveDelay" : <seconds>, "hidden" : true }
- 21. Build indexes members[n].buildIndexes : false • Can be only set when adding a member to a replica set • Can not be changed on running node • Indexes on _id will still exist • Priority must be set to 0, recommended as hidden:true Useful when • Node is used for backups using mongodump • Node does not receive queries from clients • Adding indexes and maintenance overburdens the host system
- 22. Fault tolerance Number of members Majority Required to Elect new Primary Fault Tolerance 3 2 1 4 3 1 5 3 2 6 4 2 7 4 3
- 23. Write concern
- 24. Write concern Write concern specification { w: <value>, j: <boolean>, wtimeout: <number> } • w - number – Option for “majority” • j - write operation has been written to the journal • wtimeout - time limit, in milliseconds, for the write concern Replica set get write concern setting rsTest:PRIMARY> rs.conf().settings['getLastErrorDefaults'] { "w" : 1, "wtimeout" : 0 }
- 25. Read preference • primary • primaryPreferred • secondary • secondaryPreferred • nearest
- 26. Key metrics to monitor for RS • Replica set has no Primary • Number of healthy/unhealthy members • Replication Oplog Window • Replication lag
- 27. What is MySQL Mysql is… ● Transactional ● Relational ● Well documented ● Open source
- 28. MySQL replication Mysql Replication can be... ● Asynchronous ○ Built-in replication feature ○ Semi-synchronous by plugin rpl_semi_sync_master ● Synchronous ○ Galera setup with wsrep api
- 29. MySQL replication • Group of mysqld processes that maintain the same data set • Write operations go to the Master node, reads can go to Slave • All changes are recorded into binary log on the master • Asynchronous replication, Semi-Synchronous replication • Slave node replicates the events by copying binary logs as relay logs – IO Thread, SQL Thread – Binary Logs format - Statement, Row, Mixed • Expire logs days dynamic • Replication filters
- 30. MySQL replication MySQL Master MySQL Process Binary LogsMySQL Data MySQL Slave MySQL Process SQL Thread Relay logs IO Thread MySQL Data
- 31. Questions?