Automate MongoDB with MongoDB

Management Service (MMS)

Daniel Coupal

Technical Services Engineer, MongoDB

3

Agenda

• What is MMS?

• MMS Maintenance Operations

• Demo

• MMS Monitoring

• MMS Backup

• Wrapping Up

What is MMS?

5

What WAS the MongoDB Management

Service?

• Two months 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.

6

What did we change?

• MMS is now a web-based tool that starts with

you 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!)

7

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!

8

9

And run a very large MongoDB deployment of their own!

10

11

MongoDB DatacenterCustomer Datacenter

MMS Agent

HTTPS

HTTPS

12

13

14

MMS Maintenance Operations

16

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/

17

Step 1 – Stop A Secondary

18

Step 2 – Restart As Standalone

19

Step 3 – Perform Maintenance

20

Step 4 –Restart As Member of Replica Set

21

Step 5 – Work on Primary Last

Demo

23

Operations

• Provision a cluster

• Upgrade/Downgrade

• Add replica member

• Add shard

• Remove shard

• Resize oplog

MMS Monitoring

25

Topology

26

Charting

27

Alerting

28

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 Backup

30

Risks Are Everywhere

Storage failures

Power outagesProgrammer

error

Hardware failures

AWS Mandatory

Reboots

Datacenter failures

Cyber attacks Weather

31

Replication

• Redundant copies of your data across

– Servers

– Racks

– Data Centers

• Automatic failover

• Tunable consistency minimizes risk

• However…programmer errors will replicate

almost immediately!

32

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.

33

MongoDB Backup Approaches

mongodump File system MMS Backup

Initial complexity Medium High Low

Confidence in Backups

Medium Medium High

Point in timerecovery of replica set

Sort of ☺ No Yes

System Overhead High Can be low Low

Scalable No With work Yes

ConsistentSnapshot of Sharded System

Difficult Difficult Yes

Wrapping Up

35

Roadmap

• On Premise version of automation just around

the corner

• Further support for cloud & virtualization

technologies – suggestions welcome!

36

Resources

• MMS

– mms.mongodb.com

– mms.mongodb.com/help

• MMS On-Premise

– Available with your MongoDB Entreprise Subscription

– Available for evaluation

– mms.mongodb.com/help-hosted

37

Take Away

• We are bringing the easiness of developing with

MongoDB to deploying and operating it.

Thank You for using MongoDB!

Daniel Coupal

Technical Services Engineer, MongoDB