This document summarizes new features in MongoDB versions 3.0, 3.2 and how Ops Manager can help manage MongoDB deployments. Key points include: - MongoDB 3.0 introduces pluggable storage engines like WiredTiger which offers improved write performance over MMAPv1 through document-level concurrency and built-in compression. - Ops Manager provides automation for tasks like zero downtime cluster upgrades, ensuring availability and best practices. It reduces management overhead. - MongoDB 3.2 features include faster failovers, support for more data centers, new aggregation stages, encryption at rest, partial and document level validation indexes. - Compass is a new GUI for visualizing data and performing common operations

1. MongoDB 3.x & Ops Manager
Muthu Chinnasamy
Senior Solutions Architect
muthu@mongodb.com

2. MongoDB is for…

3. Some of the Giant Ideas Using MongoDB

4. MongoDB Adds Business Value
Competitive Advantage Mitigating Risk
Lower TCOFaster Time to Value

5. Agenda
• What's new in MongoDB 3.0?
• Ops manager - Automation, backup,
monitoring
• What's new in version 3.2?
• Q&A

6. What's new in MongoDB 3.0?

8. Pluggable Storage Engines

9. Pluggable Storage Engines
Content
Repo
IoT Sensor
Backend
Ad Service
Customer
Analytics
Archive
MongoDB Query Language (MQL) + Native Drivers
MongoDB Document Data Model
MMAP V1 WT In-Memory ? ?
Supported in MongoDB 3.0 Future Possible Storage Engines
Management
Security
Example Future State
Experimental

10. Introducing WiredTiger
• Pluggable storage engines!
• MMAPv1 (Default)
• wiredTiger

11. Additional flag when launching 3.0.x mongod:
--storageEngine=wiredTiger
How Do I run WiredTiger?

12. • Cannot copy raw data files. WT will fail to start
if it finds wrong data format
• Two ways to perform an engine upgrade:
• Mongodump/Mongorestore
• Add new replica member with WT
• You can run replicas with mixed storage
engines
How Do I Upgrade to it?

13. • Document-level concurrency
• Compression
• Consistency without journaling
• Better performance for write heavy
workloads
• Vertically scalable as it allows full hardware
utilization
• Index placement on faster storage devices
Why is WiredTiger Awesome?

14. mmapv1 2.6 concurrency model
Lock manager has a toll booth for each database
Reads and writes must acquire database level lock

15. mmapv1 3.0 concurrency model
Lock manager has a toll booth for each collection
Reads and writes must acquire collection level lock

16. 7-10x Better Write Performance
No toll booths!
Atomic update replaces latching/locking
Yields on write contention to same document

17. Up to 80% Compression
• WiredTiger uses snappy compression by default
in MongoDB
• Supported compression algorithms
– snappy [default]: good compression, low overhead
– zlib: better compression, more CPU
– none
• Indexes are compressed using prefix
compression
– allows compression in RAM
500GB 100GB

18. Compression – mongod options
--wiredTigerCollectionBlockCompressor
(=snappy)
[snappy|zlib|none]
--wiredTigerJournalCompressor
(=snappy)
--wiredTigerIndexPrefixCompression
(=1)

19. Compression – Object options
db.createCollection( "coll",
{storageEngine:
{wiredTiger: { configString:
"block_compressor=snappy" }}})
db.coll.createIndex({a:1},
{storageEngine:
{wiredTiger: { configString:
"block_compressor=zlib"}}})

20. • WiredTiger cache stores uncompressed data
• Ideally, working set fits in WT cache
1. File system cache stores compressed data
2. Uses higher value of 50% of RAM or 1GB
WiredTiger Cache
--wiredTigerCacheSizeGB {arg}

21. Ensure indexes fit in RAM

22. Ops Manager

23. How Ops Manager Helps You
Scale EasilyMeet SLAs
Best Practices,
Automated
Cut Management
Overhead
23

24. Zero Downtime Cluster Upgrades
Manual Steps
• Manual steps upgrading a 2.6.11 sharded cluster to
3.0.6 version, on enterprise edition, and convert the
storage engine to wiredTiger
24
Upgrades, downgrades
150+ steps
Example Deployment – 6 Servers

25. Zero Downtime Cluster Upgrades
Ops Manager Automation
• Using Ops Manager automation
• Start with a 2.6.11 Community cluster
• Upgrade to 3.0.6 Enterprise cluster
• Convert storage Engine to wiredTiger
Turn long and complicated manual processes into
single click operations with Ops Manager automation
Ensure availability during system upgrades
25

26. Summary: Benefits of MongoDB 3.0

27. What's new in version 3.2

28. New in MongoDB 3.2

29. MongoDB 3.2 New Features
• Fast failovers
– 2-seconds election times
• Support for more than 3 data centers
– Config servers as replica sets
• Cluster read-committed
– readConcern: { level: <majority|local>
• WiredTiger default storage engine
• Aggregation framework enhancements
– New stages $sample
– New arithmetic operators & accumulators
• Mongo shell enhancements

30. MongoDB 3.2 – Compass

31. MongoDB 3.2 – Left Outer Joins
• Create a new field in aggregated documents "cust_orders"
containing array of documents from "orders" collection
• Similar to where "customers"."_id"="orders"."cust_id"
Db.customers.aggregate([
{
$lookUp:
{ from: "orders",
localField: "_id",
foreignField: "cust_id",
as: "cust_orders"
}
}
])

32. MongoDB 3.2 – Encryption at rest
• Encryption is a database-level option
– Master key & local keys allow for easier key
management and key rotation for compliance
• Supports standard 3rd party key management
appliances (KMIP)
• Default encryption schema is AES256-CBC
– Also have GCM
• FIPS 140-2 compliant option

33. MongoDB 3.2 – Partial Indexes
> db.customers.createIndex({ state:1}, { partialFilterExpression: { active: {$eq : 'Y'}}})
{
"createdCollectionAutomatically" : false,
"numIndexesBefore" : 1,
"numIndexesAfter" : 2,
"ok" : 1
}
Index only for docs
matching the filter
expression

34. MongoDB 3.2 – Document Validation
> db.runCommand({"collMod": 'customers', "validator" : {email: {$exists: true}}})
{ "ok" : 1 }
> db.customers.insert({name:'Rose McClendon', age:27, state:'CA', city:'San Francisco',
zip:94301})
WriteResult({
"nInserted" : 0,
"writeError" : {
"code" : 121,
"errmsg" : "Document failed validation"
}
})
> db.customers.insert({name:'Rose McClendon', age:27,
email:'rose.mcclendon@cox.net', state:'CA', city:'San Francisco', zip:94301})
WriteResult({ "nInserted" : 1 })
Enforces
email field

35. Thank You!
Questions?