How to Automate, Monitor and Manage your MongoDB Servers
summary
Shows how to automate a three‑node replica set deployment with Chef MongoDB 3 cookbook, Puppet, Ansible or Salt instead of manual installs, integrates MMS/Cloud Manager or MMS automation agent, and scripts backups via mongodump or mongo-backup and filesystem snapshots (LVM, ZFS, XFS, EBS). Recommends monitoring replication lag and oplog size across every node, trending with statsd/Graphite/Grafana or Zabbix, and tying backups to chatbots like Hubot; notes default oplog ≈ 5% of disk and ClusterControl for end‑to‑end orchestration.
AI-written summary · about
chapters (31)
- 0:00Intro
- 0:47MongoDB: why should I install it?
- 1:23Polyglot Persistence?
- 1:55Monoglot Persistence
- 2:36How different is MongoDB from MySQL?
- 3:22Eventual consistency
- 4:23Install MongoDB
- 4:43Configure MongoDB
- 5:02Install a third node
- 5:13Deployment Automation
- 5:59Puppet
- 8:20Saltstack
- 9:23Monitoring vs Trending
- 10:07Monitoring: Availability
- 12:23Monitoring Tools
- 14:10Trending: Why do we need trends?
- 16:34Trending: What metrics to store?
- 17:46Trending: Solutions
- 18:18Cacti
- 19:03Types of backups
- 19:44Logical backups: mongodump
- 20:14Logical backups: MongoDB Backup
- 21:56Logical backups: Mongob
- 22:54Physical backups: Filesystem snapshots
- 23:31Physical backups: Strata
- 24:24Why do schemas need changes?
- 25:15Schema changes for MySQL
- 26:20Schema Validation
- 27:39Schema Analyzer
- 28:51Orchestration systems: Mongoct
- 29:18Orchestration Systems: ClusterControl
related talks
32mAutomating high availability MongoDB cluster deployment and management
37mBuilding MongoDB Replica
26mConsistent Backups for Multi-Shard MongoDB
35mBeyond Rapid Development - Jason Mimick
40mMongoDB Backups Overview
29mMulti Active-Active and disaster recovery with MongoDB database center
36mUnderstanding all the Options for Replica-sets and Replication Patterns
26mCurrent state of MongoDB Backup options