Run MongoDB with Confidence using MMS

Sam Weaver

#mongodb #mongodbdays

@samuel_weaver

Product Manager, MongoDB

Operational complexities

What is MMS?

MMS back in the day

What WAS the MongoDB Management Service?

• Two weeks ago, the MongoDB Management Service was a web-based tool that allowed you to Monitor and Backup your MongoDB deployment.

• You created your deployment, in any size or shape, then you used MMS to Monitor or Backup your deployment.

What did we change?

• MMS is now a web-based tool that starts with your from the beginning of your MongoDB deployment lifecycle.

• Now you use MMS to build your deployment, and then continue to use MMS to manage its lifecycle (including Monitoring and Backup!)

Why the change?

1. MMS was arriving in the user’s life a little “late to the party”. Mistakes had already been made. User might already some misconceptions or frustrations with MongoDB.

2. Previous version of MMS could monitor critical operations (maintenance, upgrades, etc.), but not actually help!

3. Puppet/Chef/Others scripts hard to maintain between version releases. Lots can go wrong!

MongoDB DatacenterCustomer Datacenter

MMS Agent

HTTPS

HTTPS

Onboarding Demo

MMS Monitoring

Topology

Charting

Alerting

Proactive Support

MongoDB offers Proactive Support for Subscription Customers. Our

engineers can monitor your deployment and make suggestions in

order to tweak for better performance or avoid doom.

MMS Backups

Risks Are Everywhere

Storage failures

Power outages

Programmer error

Hardware failures

AWS Mandatory

Reboots

Datacenter failures

Cyber attacks Weather

Replication

• Redundant copies of your data across– Servers– Racks– Data Centers

• Automatic failover

• Tunable consistency minimizes risk

• However…programmer errors will replicate almost immediately!

Backups

Backing up data is one way to ensure availability and lower risk. Effort is required to ensure that your backup system is always running and that the backups are correct.

MongoDB Backup Approaches

mongodump File system MMS Backup

Initial complexity

Medium High Low

Confidence in Backups

Medium Medium High

Point in time recovery of replica set

Sort of ☺ No Yes

System Overhead

High Can be low Low

Scalable No With work Yes

Consistent Snapshot of Sharded System

Difficult Difficult Yes

Queryable Backups Demo

MMS Maintenance Operations

The Process

• Applies to upgrades and most maintenance tasks

• Careful order of steps is critical– Especially in sharded clusters!

• For each shard/replica set– For each replica set member

• http://docs.mongodb.org/manual/tutorial/perform-maintence-on-replica-set-members/

Step 1 – Stop A Secondary

Step 2 – Restart As Standalone

Step 3 – Perform Maintenance

Step 4 – Restart As Member of Replica Set

Step 5 – Work on Primary Last

Demo

Operations

• Upgrade/Downgrade

• Add replica member

• Add shard

• Remove shard

• Resize oplog

Roadmap

• On Premise version of automation just around the corner

• Further support for cloud & virtualization technologies – suggestions welcome!

Resources

• MMS– mms.mongodb.com– mms.mongodb.com/help

• MMS On-Premise– Available for evaluation– mms.mongodb.com/help-hosted

Thank You

Sam Weaver

#mongodb #mongodbdays

@samuel_weaver

Product Manager, MongoDB