MongoDB Management Service (MMS) is a suite of services for managing MongoDB deployments. Engineered by the team who develops MongoDB, MMS makes it easier to operate MongoDB at any scale. MMS provides monitoring, backup and recovery, helping users optimize clusters and mitigate operational risk. MMS users can visualize database performance and set custom alerts that notify when particular metrics are out of normal range. MMS is also the only continuous backup solution for MongoDB, providing point-in-time recovery for replica sets and cluster-wide snapshots of sharded systems. MMS is available as a fully managed cloud service, or as on-prem software included with your MongoDB Enterprise subscription. Benefits of MMS: • Knowledge. • Confidence. • Visibility.

1. MongoDB Management Service
(MMS)
Overview
Angshuman Bagchi (angshuman.bagchi@mongodb.com)
Technical Services Engineer

2. Agenda
• What is MMS?
– Monitoring
• Why use MMS Monitoring?
• Setting it up and getting around
• Performance and monitoring
– Backup
• Risks
• Backup strategies
• Wrap up

3. What is MMS Monitoring?

4. Demo

5. What’s in it for me?
• Great high level view + detailed metrics
• Low effort, high-return
• Makes it easier for us to help you!

6. How do I use this crazy thing?
http://mms.mongodb.com/help/monitoring/tutorial/

7. Performance tuning
and monitoring

8. Pro-Tip: know thyself
You have to recognize normal to know when it isn’t.
Source: http://www.flickr.com/photos/skippy/6853920/

9. Finding the bottleneck
Source: http://www.flickr.com/photos/laenulfean/462715479/

10. Some handy metrics to watch
•
•
•
•
•
•
Memory usage
Opcounters
Lock %
Queues
Background flush average
Replication stats

11. Example: replication lag
150,000s of lag ~ almost 2 days of lag!

12. Example: replication lag
• Secondaries under specified vs primaries
• Access patterns between primary /
secondaries
• Insufficient bandwidth
• Foreground index builds on secondaries
“…when you have eliminated the impossible, whatever remains,
however improbable, must be the truth…” -- Sherlock Holmes
Sir Arthur Conan Doyle, The Sign of the Four

13. Example: replication lag
Example:
• ~1500 ops per minute (opcounters)
• 0.1 MB per object (average object size,
local db)
~1500 ops/min / 60 seconds * 0.1 MB/op *
8b/B =~ 20 mbps required bandwidth

14. MMS Backup

15. Disaster do happen …
... sometimes they are our fault

16. Availability & Durability
risks
[
{
"failure" : [
"storage",
"power",
"host",
"dataCenter"
]
},
"programmerError",
"cyberAttack"
]

17. Addressing Risks
• Relative to any particular risk
source:http://www.definethecloud.net/
• Solutions
– Replication
– Backup

18. Replication
… but programmer errors …
… garbage in => garbage out

19. Backup
•
•
•
•
•
Much slower to restore (availability suffers)
Out of date to some extent
Fairly cheap
Well isolated
Handles almost all risks

20. Backup Approaches
• mongodump/mongorestore
• Storage-level options
• MongoDB Backup Service (new!)

21. mongodump / mongorestore
•
•
•
•
Can be run in live or offline mode
Oplog-aware for point-in-time operations
Filter can be applied in both directions
Considerations
– Working set
– Sharding

22. Storage-level Backups
• Copy files in your data directory (e.g.
/data/db)
• Filesystem or block storage snapshot
• Fastest way to backup/restore
• Considerations
– Consistency
– Backup granularity
– Ops expertise

23. MMS Backup : Overview

24. Recovery Approaches
Mongodump
Initial complexity
Time to restore
Point in time
recovery of replica
set
System Overhead
Scalable
Consistent
Snapshot of
Sharded System
File system
MMS Backup

25. How much does it cost?
• Free Tier - monthly bill under $5 is free for first 12 months

26. Summary
•
•
•
•
MMS Monitoring is a great, free service
Setup is easy
Proactively monitor your cluster
MMS Backups makes backing up data
easy
• Making MongoDB operations as easy as
development using MongoDB