MongoDB Management Service
(MMS)
Overview
Angshuman Bagchi (angshuman.bagchi@mongodb.com)
Technical Services Engineer
Agenda
• What is MMS?
– Monitoring
• Why use MMS Monitoring?
• Setting it up and getting around
• Performance and monitori...
What is MMS Monitoring?
Demo
What’s in it for me?

• Great high level view + detailed metrics
• Low effort, high-return
• Makes it easier for us to hel...
How do I use this crazy thing?
http://mms.mongodb.com/help/monitoring/tutorial/
Performance tuning
and monitoring
Pro-Tip: know thyself
You have to recognize normal to know when it isn’t.

Source: http://www.flickr.com/photos/skippy/685...
Finding the bottleneck

Source: http://www.flickr.com/photos/laenulfean/462715479/
Some handy metrics to watch
•
•
•
•
•
•

Memory usage
Opcounters
Lock %
Queues
Background flush average
Replication stats
Example: replication lag
150,000s of lag ~ almost 2 days of lag!
Example: replication lag
• Secondaries under specified vs primaries
• Access patterns between primary /
secondaries
• Insu...
Example: replication lag
Example:
• ~1500 ops per minute (opcounters)
• 0.1 MB per object (average object size,
local db)
...
MMS Backup
Disaster do happen …
... sometimes they are our fault
Availability & Durability
risks
[
{
"failure" : [
"storage",
"power",
"host",
"dataCenter"
]
},
"programmerError",
"cyberA...
Addressing Risks
• Relative to any particular risk

source:http://www.definethecloud.net/

• Solutions
– Replication
– Bac...
Replication

… but programmer errors …
… garbage in => garbage out
Backup
•
•
•
•
•

Much slower to restore (availability suffers)
Out of date to some extent
Fairly cheap
Well isolated
Hand...
Backup Approaches
• mongodump/mongorestore
• Storage-level options
• MongoDB Backup Service (new!)
mongodump / mongorestore
•
•
•
•

Can be run in live or offline mode
Oplog-aware for point-in-time operations
Filter can b...
Storage-level Backups
• Copy files in your data directory (e.g.
/data/db)
• Filesystem or block storage snapshot
• Fastest...
MMS Backup : Overview
Recovery Approaches
Mongodump
Initial complexity
Time to restore
Point in time
recovery of replica
set
System Overhead
Sca...
How much does it cost?
• Free Tier - monthly bill under $5 is free for first 12 months
Summary
•
•
•
•

MMS Monitoring is a great, free service
Setup is easy
Proactively monitor your cluster
MMS Backups makes ...
Upcoming SlideShare
Loading in …5
×

MongoDB Management Service Overview

1,929 views

Published on

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.

Published in: Technology
0 Comments
8 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,929
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
68
Comments
0
Likes
8
Embeds 0
No embeds

No notes for slide
  • Talk about fat finger wall street trader.http://en.wikipedia.org/wiki/2010_Flash_Crash
  • How much data can you afford to lose? (RPO)How long can you afford to be off-line? (RTO)What price are you willing to pay to remove or mitigate the risk.
  • Mulitple copies of garbage for replication – for that you need backup. MongoDB built it for you, so only has devops and infrastructure cost.Lose very little to zero data in a failureDown for a very short interval (availability is high)BUT: programmer errors, deliberate data loss is often replicated nearly instantly.
  • Mention backup strategies document.
  • From the initial sync, we rebuild your data in our datacenters and take a snapshotWe take snapshots every 6 hoursOplog is stored for 48 hoursBalancer paused every 6 hours A no-op token is inserted across all shards, mongos’s and config serversOplog applied to replica sets until point in which token was insertedProvides a consistent state of database across shards
  • MongoDB Management Service Overview

    1. 1. MongoDB Management Service (MMS) Overview Angshuman Bagchi (angshuman.bagchi@mongodb.com) Technical Services Engineer
    2. 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. 3. What is MMS Monitoring?
    4. 4. Demo
    5. 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. 6. How do I use this crazy thing? http://mms.mongodb.com/help/monitoring/tutorial/
    7. 7. Performance tuning and monitoring
    8. 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. 9. Finding the bottleneck Source: http://www.flickr.com/photos/laenulfean/462715479/
    10. 10. Some handy metrics to watch • • • • • • Memory usage Opcounters Lock % Queues Background flush average Replication stats
    11. 11. Example: replication lag 150,000s of lag ~ almost 2 days of lag!
    12. 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. 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. 14. MMS Backup
    15. 15. Disaster do happen … ... sometimes they are our fault
    16. 16. Availability & Durability risks [ { "failure" : [ "storage", "power", "host", "dataCenter" ] }, "programmerError", "cyberAttack" ]
    17. 17. Addressing Risks • Relative to any particular risk source:http://www.definethecloud.net/ • Solutions – Replication – Backup
    18. 18. Replication … but programmer errors … … garbage in => garbage out
    19. 19. Backup • • • • • Much slower to restore (availability suffers) Out of date to some extent Fairly cheap Well isolated Handles almost all risks
    20. 20. Backup Approaches • mongodump/mongorestore • Storage-level options • MongoDB Backup Service (new!)
    21. 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. 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. 23. MMS Backup : Overview
    24. 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. 25. How much does it cost? • Free Tier - monthly bill under $5 is free for first 12 months
    26. 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

    ×