This blog post is the first in a series on Percona’s MongoDB 3.4 bundle release. This release includes Percona Server for MongoDB, Percona Monitoring and Management, and Percona Toolkit. In this post, we’ll look at the features included in the release.
We have a lot of great MongoDB content coming your way in the next few weeks. However, I wanted first to give you a quick list of the major things to be on the look out for.
This new bundled release ensures a robust, secure database that you can adapt to changing business requirements. It helps demonstrate how organizations can use MongoDB (and Percona Server for MongoDB), PMM and Percona Toolkit together to benefit from the cost savings and agility provided by free and proven open source software.
Percona Server for MongoDB 3.4 delivers all the latest MongoDB 3.4 Community Edition features, additional Enterprise features and a greater choice of storage engines.
Some of these new features include:
- Shard member types. All nodes now need to know what they do – this helps with reporting and architecture planning more than the underlying code, but it’s an important first step.
- Sharding balancer moved to config server primary
- Configuration servers must now be a replica set
- Faster balancing (shard count/2) – concurrent balancing actions can now happen at the same time!
- Sharding and replication tags renamed to “zones” – again, an important first step
- Default write behavior moved to majority – this could majorly impact many workloads, but moving to a default safe write mode is important
- New decimal data type
- Graph aggregation functions – we will talk about these more in a later blog, but for now note that graph and faceted searches are added.
- Collations added to most access patterns for collections and databases
- . . .and much more
- Integrated, pluggable authentication with LDAP that provides a centralized enterprise authentication service
- Open-source auditing for visibility into user and process actions in the database, with the ability to redact sensitive information (such as user names and IP addresses) from log files
- Hot backups for the WiredTiger engine to protect against data loss in the case of a crash or disaster, without impacting performance
- Two storage engine options not supported by MongoDB Community Edition 3.4 (doubling the total engine count choices):
- Support for MongoDB and Percona Server for MongoDB
- Graphical dashboard information for WiredTiger, MongoRocks and Percona Memory Engine
- Cluster and replica set wide views
- Many more graphable metrics available for both for the OS and the database layer than currently provided by other tools in the ecosystem
- Two new tools for MongoDB are now in Percona’s Toolkit:
- pt-mongodb-summary (the equivalent of pt-mysql-summary) provides a quick, at-a-glance overview of a MongoDB and Percona Server for MongoDB instance
- This is useful for any DBA who wants a general idea of what’s happening in the system, what the state of their cluster/replica set is, and more.
- pt-mongodb-query-digest (the equivalent of pt-query-digest for MySQL) offers a query review for troubleshooting
- Query digest is one of the most used Toolkit features ever. In MongoDB, this is no different. Typically you might only look at your best and worst query times and document scans. However, this will show 90th percentiles, and top 10 queries take seconds versus minutes.
For all of these topics, you will see more blogs in the next few weeks that cover them in detail. Some people have asked what Percona’s MongoDB commitment looks like. Hopefully, this series of blogs help show how improving open source databases is central to the Percona vision. We are here to make the world better for developers, DBAs and other MongoDB users.