Run MongoDB with Confidence Using MongoDB Management Service (MMS)
•Télécharger en tant que PPTX, PDF•
3 j'aime•1,716 vues
MongoDB Management Service (https://mms.mongodb.com/) can help you run MongoDB with confidence. MMS provides visibility into the performance of your cluster, alerting when key metrics are out of range and backup and recovery of your mission critical data. This free session will provide you with an overview of MMS, including installation and setup, a walk through of metrics and alerts, as well as a deep dive on how backup works.
Recommandé
Recommandé
Contenu connexe
Plus de MongoDB
Plus de MongoDB (20)
Dernier
Dernier (20)
Run MongoDB with Confidence Using MongoDB Management Service (MMS)
- 1. MongoDB Management Service (MMS) Rick Houlihan Solutions Architect
- 2. 2 Agenda Introduction MMS Monitoring Overview Setup Demo MMS Backup Overview Summary
- 3. 3 MMS Introduction What is it? MongoDB Management Service (MMS) is an enterprise grade platform built to manage any size MongoDB deployment. • Real Time Monitoring • Alert/Notification API • Point in Time Backup • Automation (Coming Soon!)
- 4. 4 MMS Monitoring How it works
- 5. 5 MMS Monitoring Dashboards and Metrics • Multi-level Operational Dashboards • Customizable Charts • Metrics by Host or Group • Flexible Log Collection • Per Host or Global • Detailed Metric Breakdowns • Server Event Annotations
- 6. 6 MMS Monitoring Running with Confidence • Configurable Alerts • Critical Database KPI’s • Host Configuration and Status • Host Level Metrics • Flexible Notifications • Tiered Alert Scheduling • SMS, Email • Third Party Integrations • PagerDuty, HipChat, SNMP
- 7. 7 MMS – Get Started Fast • Create an MMS Group • http://mms.mongodb.com (cloud) • http://yourhost:8080 (on prem) • Install the Agent(s) • Monitoring is required • Backup is optional • Start Managing MongoDB!
- 8. 8 MMS Backup How it works
- 9. 9 MMS GroupMMS GroupMMS Group MMS Group MMS Agent MMS Backup – Agent Overview Replica Set Replica Set Replica Set mongodmongodmongod MMS Service • Flexible Deployment Options • Statically compiled Go binary • One agent per MMS group • Stateless • Workflow Monitor and Control Point • Sends initial sync and oplog data • Synchronizes shards and config servers • Shared or Dedicated Host • Can be network and CPU intensive
- 10. 10 Works Like A Secondary • Fully Automated Process • Oplog replayed on backup host • Concurrent backup of multiple clusters • Support for multiple mongod versions • Standard Replication Mechanisms • Proven and reliable at scale • No replica set configuration required Configuration Initial Sync Oplog Tail Oplog Replay Snapshot • Minimal Production Impact • Incremental oplog traffic after initial sync
- 11. 11 System Architecture Reconstructed Replica Sets Backup Agent Replica Set 1 Customer Backup Ingestion MongoDB Inc. Backup Daemon Data DB Block Store Replica Set 1 1. Configuration 2. Initial Sync 3. Stream Oplog 4. Store Data 7. Persist Snapshot 5. Retrieve Data 6. Apply Ops
- 12. 12 MMS Backup - Daemon • Asynchronous Backup Process • Data is processed from raw oplog cache • Oplog replay executed on source mongod version • Snapshot is de-duped at file and block level to minimize footprint on disk • Concurrent Replica Set Backup • Manages simultaneous backup of multiple replica sets • Maintains version consistency with source • User Configurable Snapshots • Adjustable snapshot scheduling and persistence requirements
- 13. 13 MMS – Single Server Deployment
- 14. 14 MMS - Large Deployment with HA
- 15. 15 MMS - Hosted Service Deployment Meta Data DB Oplog DB Sync DB Blockstore DB (6x) Daemon Host (15x across 2 DCs) 16 CPU cores, 386 GB RAM, 36 disks Ingest 4x 2 per DC Restore 2x 1 per DC Partition 0 (17-20TB 7.2k RAID 10) – One of the DBs Partition 1 (17-20TB 7.2k RAID 10) – One of the DBs Partition 2 (2-3.5TB SSD or 15k RAID 0) – Daemon heads Partition 3 (2-3.5TB SSD or 15k RAID 0) – Daemon heads Daemon Process 1 (Java) Daemon Process 2 (Java)
- 16. 16 • Fully Integrated Management Service for MongoDB – Leverages operational best practices for Monitoring and Backup – Provides Point in Time Snapshot and Recovery – Supported by MongoDB • Flexible Deployment Options – Available hosted or on prem – Flexible Alerts and Notifications – Tunable snapshots and persistence scheduling • Distributed and Scalable – Multi tiered architecture – Horizontally scalable to meet business requirements MMS - Summary
- 17. 17 MMS - Learn More and Sign Up http://mms.mongodb.com
- 18. 18 MongoDB World New York City, June 23-25 http://world.mongodb.com Save $200 with discount code MODERNAPPS #MongoDBWorld See how Bosch, UK Government Digital Service, Carfax, Stripe and others are engineering the next generation of data with MongoDB
Notes de l'éditeur
- Speak to audience, who the target is and why:Developers for debug and testDBA’s for runtime optimization and performance profilingOperations for monitoring, alerting, backup, and operational analytics
- TOUCH ON BEST PRACTICES
- Consists of core services that run either in the cloud or on prem and MMS Agents that run locally and pull configuration data from the MMS serviceData is collected on a regular interval from mongod instances, replica sets, and sharded clusters.Data is aggregated and queued and uploaded to the MMS cloud service or on prem MMS instance.Sounds simple, but its reeally not.Fully integrated infrastructure for processing aggregated metrics across mongodb clusters, backed by MongoDB, and built for high volume data ingestion.Mirrors commonly implemented monitoring solutions for mission critical applications.
- Expand on metrics by group – Cluster/Shard/Host/Type aggregations provide drill down operational views
- Alert on any metric, integrate with existing operations consoles and notification managers.
- HIT ON OPERATIONAL BEST PRACTICESAdd on component for MMSRelies on info collected by MonitoringConfiguration UI and Alerts in MMS ConsoleMMS Admin UI integrationConsistent, Reliable, and StablePoint in Time Backup and Restore for MongoDB Clusters Designed from the ground up to leverage operational best practices Supported directly by MongoDB and built for enterprise scaleHosted Service or On PremLeverage off site backup to the Mongo MMS CloudDeploy internally for large scale or high security environments
- Only piece of on prem software required for cloud deploymnentsNative installers available for Redhat, CentOS, SUSE, AWS Linux, Ubuntu, Windows, and MacOS.
- Completely stateless, will pull down configuration from MMS on startupLocal oplog cache is transient, agent will resume oplog tail from last timestamp sent by MMSIf offline for too long (Oplog rollover), full resync is required before snapshots can resume
- HIT ON COMPLEXITY OF IMPLEMENTATION FOR POINT IN TIME BACKUPREINFORCE BEST PRACTICESBackup Agent = External program, similar to MMS Agent. Written in Go.Ingestion = RESTful interface. Responsible for all agent communication (configuration and ingestion)Daemons = Background process that does actual processing
- Oplog DB – DB per MMS group, collection per replica setSync DB – DB per replica setBlockstore DB – application sharded. DB per replica set + metadata35K MMS Users500 Customers