Skip to content

Percona Distribution for MongoDB 5.0.7

Date

April 20, 2022

Installation

Installing Percona Distribution for MongoDB

Percona Distribution for MongoDB is a freely available MongoDB database alternative, giving you a single solution that combines enterprise components from the open source community, designed and tested to work together. The aim of Percona Distribution for MongoDB is to enable you to run and operate your MongoDB efficiently with the data being consistently backed up.

Percona Distribution for MongoDB includes the following components:

  • Percona Server for MongoDB is a fully compatible open source, drop-in replacement for MongoDB.

  • Percona Backup for MongoDB is a distributed, low-impact solution for achieving consistent backups of MongoDB sharded clusters and replica sets.

This release of Percona Distribution for MongoDB is based on Percona Server for MongoDB 5.0.7-6 and Percona Backup for MongoDB 1.7.0.

Important

To make physical backups and restores, the pbm-agent must have the read / write access to the dataDir. If you use the filesystem-based backup storage, the pbm-agent must also have the read / write access to the backup directory. Therefore, starting from version 1.7.0, the user running the pbm-agent is changed from pbm to mongod in Percona Backup for MongoDB packages.

To upgrade Percona Backup for MongoDB to version 1.7.0, do the following:

  1. Stop the pbm-agent process

  2. Upgrade new version packages

  3. Reload the systemd process to update the unit file with the following command:

    $ sudo  systemctl daemon-reload

  1. If you have a filesystem-based backup storage, grant read / write permissions to the backup directory to the mongod user.

  2. Restart the pbm-agent process.

If MongoDB runs under a different user than mongod (the default configuration for Percona Server for MongoDB), use the same user to run the pbm-agent. For filesystem-based storage, grant the read / write permissions to the backup directory for this user.

Release Highlights

This release of Percona Distribution for MongoDB includes the support of Keys Management Interoperability Protocol (KMIP). Thus, users can store encryption keys in their favorite KMIP-compatible key manager to set up encryption at rest. This is a tech preview feature.

The most notable bug fixes, provided by MongoDB and included in Percona Server for MongoDB are the following:

  • Fixed the issue where having a large number of split points causes the chunk splitter to not function correctly and huge chunks would not be split without manual intervention. This can be caused when having small shard key ranges and a very high number of documents and where more than 8192 split points would be needed.

  • Recover the RecoverableCriticalSection service after the initialSync and startupRecovery stages have completed. This prevents a started up shard to miss an in-memory critical section of a resharded collection.

  • Fixed an issue that occurred during the attempt to perform the collation-encoding of a document with a missing sort attribute. In this case an invariant is violated and mongod crashes.

  • Fixed an issue when the rename collection (sharding step) participants can get stuck.

  • Fixed an issue with idle cursors remaining open when the client attempts to run an aggregation with $out or $merge in a transaction on a sharded cluster.

  • Check if the host has cgroups v2 enabled and read the memory limits according to that.

  • Report an error when the WiredTiger version file is empty or missing during a startup.

Percona Backup for MongoDB 1.7.0 improvements include the following:

  • Support for physical backups in Percona Server for MongoDB starting from versions 4.2.15-16 and 4.4.6-8 and higher. Physical backups drastically speed up backup and restore performance for large databases (several terabytes). This is a technical preview feature.

  • Oplog replay from the arbitrary start time. This reduces Recovery Point Objective (RPO) when database is recovered from physical or storage-level backups.

  • Ability to configure compression method and level for point-in-time recovery chunks and compression level for backups.

  • Ability to configure the number of S3 multipart upload chunks to comply with various S3-compatible storage provider requirements.

  • Ability to configure the number of upload retries. This facilitates data upload in case of unstable network connection.