Skip to content
Percona Software for MongoDB Documentation

For help, click the link below to get free database assistance or contact our experts for personalized support.

Get help from Percona

Percona Server for MongoDB 7.0.18-11 (2025-04-24)

Installation Upgrade from MongoDB Community

Percona Server for MongoDB 7.0.18-11 is an enhanced, source-available, and highly-scalable database that is a fully-compatible, drop-in replacement for MongoDB Community Edition.

Percona Server for MongoDB 7.0.18-11 includes the improvements and bug fixes of MongoDB 7.0.17 Community Edition and MongoDB 7.0.18 Community Edition. It supports its protocols and drivers of both MongoDB 7.0.17 and MongoDB 7.0.18.

Release Highlights

This release provides the following features and improvements:

Improved compatibility for data-at-rest encryption using KMIP between Percona Server for MongoDB and MongoDB Enterprise Advanced

We have added the security.kmip.useLegacyProtocol configuration option to improve compatibility of Percona Server for MongoDB with MongoDB Enterprise Edition. This enables you to migrate from MongoDB Enterprise Advanced to Percona Server for MongoDB without having to modify the configuration file. Since Percona Server for MongoDB uses KMIP protocol version 1.0 by default, it ignores this option and prints the log message about it.

Audit log improvements

Enjoy a better user experience with these improvements to audit logging:

  • You can output logging information either to a syslog, a file or to print in the console. Now Percona Server for MongoDB correctly parses the specified destination and creates a logging file only if you explicitly defined the file as its value. This helps keep the system clean from unnecessary files
  • By default, Percona Server for MongoDB saves the log file at the server’s configured log path or to a directory from where mongod was started if the server’s log path is undefined. You can also set a custom path to output a log file. For both cases, Percona Server for MongoDB checks if the audit log file can be opened for writing to ensure that logging information is written and available.

Debug symbols added in Percona Server for MongoDB Pro binaries

With this release, Percona Server for MongoDB Pro packages and binary tarballs include binaries that contain debug symbols. This changes makes Percona Server for MongoDB Pro compatible for runtime instrumentation to collect more detailed telemetry data and have improved monitoring.

By integrating Percona Server for MongoDB Pro with advanced monitoring tools that use debug symbols, you have a deeper visibility into the server and receive detailed diagnostic data and logs.

Compatibility with Amazon Linux 2023

We build and test Percona Server for MongoDB only on the latest versions of Amazon Linux 2023. Because of the way Amazon Linux updates their libraries, Percona Server for MongoDB 7.0.18-11 is compatible only with Amazon Linux 2023.7.x and won’t work on Amazon Linux 2023.6.x and older.

To upgrade to 7.0.18-11, make sure that you run Amazon Linux 2023.7.x. Use the update instructions

Upstream Improvements

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

  • SERVER-73641 - Fixed the issue with timeseries filtering missing extended-range events when sharded by generating timeseries _id comparisons only on mongod nodes
  • SERVER-76883 - Improved logging behavior for roles not being mapped to users to throw a warning for internally-authorized users and to show this message with higher log verbosity level for externally-authorized users so that this message can be suppressed
  • SERVER-85627 - Extended logs for a thread is interrupted by replica set stage change with details like thread name and the reason for its interruption
  • SERVER-89614 - Added enumeration to track the cleanup state for $out stage to properly drop buckets collection during interrupt
  • SERVER-95452 - Prevented CollectionRoutingInfoTargeter from iterating all chunk ranges during update and delete to improve performance
  • SERVER-98720 - Added redaction of the BSON command for “Plan executor error” warning logs to prevent the entire command text (possibly including PII) to end up in the logs
  • SERVER-100901 - Reduce the strictness of an invariant check for the unique ID (uid) in the session identifier (lsid) to match between the operation’s context (opCtx) and the incoming command request by treating it as a code error, logging it and have the server continue operating

Find the full list of changes in the MongoDB 7.0.17 Community Edition release notes and MongoDB 7.0.18 Community Edition release notes.

Changelog

New Features

  • PSMDB-1282 - Add the security.kmip.useLegacyProtocol config file option to simplify migration from MongoDB Enterprise Edition to Percona Server for MongoDB

Improvements

  • PSMDB-1620 - Do not create an empty audit log file if the log destination is not file

  • PSMDB-1621 - Check if an audit log file can be opened for writing at default path

Fixed Bugs

  • PSMDB-118 - Fixed the audit log file extension to be created based on the specified audit log format.

  • PSMDB-121 - Fixed the issue with the server failing to create an audit log file at the user provided path when the process is forked and the relative path is given by converting it to an absolute path

  • PSMDB-1227 - Improved handling of LDAP queries that contain the Distinguished Name (DN) value in the attributes part. Now the DN is treated the same way as an empty string to be more compatible with commonly used configurations

  • PSMDB-1392 - Ensured that $backupCursor returns oplogEnd without holes (Thank you MingTotti Guoming He for reporting this issue)

  • PSMDB-1614 - Replaced a hard-coded port number with a placeholder in percona-server-enable-authentication.sh

  • PSMDB-1617 - Improved error messages when there are insufficient permissions to access client/CA certificates for KMIP authentication