Percona Server for MongoDB 8.0.16-5 (2025-12-02)¶

Install Upgrade from MongoDB Community

Percona Server for MongoDB 8.0.16-5 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 8.0.16-5 includes the improvements and bug fixes of the following versions of MongoDB Community Edition:

Percona Server for MongoDB 8.0.16-5 supports protocols and drivers of MongoDB Community 8.0.13 through 8.0.16.

Release Highlights¶

This release provides the following features and improvements:

No vendor lock-in with OpenBao support for data-at-rest encryption¶

To give you more flexibility for enterprise-grade data encryption, Percona Server for MongoDB now supports OpenBao in addition to HashiCorp Vault. OpenBao is the open-source fork of Vault, providing the same powerful security while helping you avoid vendor lock-in.

This enhancement reflects our commitment to giving you more control over your security architecture while maintaining the reliability and performance you expect from Percona.

For guidance on configuring OpenBao, check our documentation.

Sunsetting Pro Builds¶

In line with our open‑source mission, we are officially sunsetting Pro Builds. All features that were previously included in Pro Builds are now accessible to everyone in our regular public builds.

If you require a Pro Build for a previously released version, your Percona representative is ready to guide you. Our goal is to ensure a smooth transition and continued success with Percona open‑source solutions, enhanced with enterprise‑grade capabilities.

Official support of Rocky Linux 8 and 9¶

Percona Server for MongoDB is now officially supported and tested on Rocky Linux 8 and 9. The fully supported status for Rocky Linux gives you confidence to run production workloads on a community‑driven, enterprise‑ready operating system.

Upstream Improvements¶

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

SERVER-77172 - Fixed a bug where checkShardingCatalogConsistency could incorrectly report a cluster is inconsistent due to an assertion failure when processing the results of the sh.status() command. This fix resolves the assertion failure, preventing false inconsistency reports.
SERVER-82180 - Fixed an issue where capped collection inserts on the primary could result in a different natural ordering compared to secondaries. This divergence in ordering between replica set members is now corrected, ensuring consistency in data placement and retrieval for capped collections across the replica set.
SERVER-91686 - Improved mongod’s signal handler to print out current thread’s command object. This enhancement provides crucial diagnostic information to aid in debugging server issues.
SERVER-94315 - Fixed the issue with shard filtering on a collection with non-simple default collation that is sharded on a field where the backing index has a simple collation. Shard filtering is now applied for non-simple collation find on sharded collections.
SERVER-102670 - Fixed an issue that caused incorrect error handling during ordered time-series inserts by clearing errors before retrying.
SERVER-107361 - Fixed a critical issue in time-series bucket rollover determination that could lead to schema mix-up for large measurements. The rollover logic previously failed to perform essential schema incompatibility checks when a bucket was kept open due to large measurement size, which could result in a single bucket containing mixed schema data. The fix ensures that schema checks are always performed. Impacted users must upgrade to a fixed version and set the timeseriesBucketsMayHaveMixedSchemaData to true for each affected collection to ensure that future queries on the collection return correct results. Refer to upstream remediation steps for a complete step-by-step guide on how to resolve the impacted collections.
SERVER-100448 - Fixed the issue with command registration depending on the Feature Compatibility Version (FCV) during startup. The command registration is no longer independent of the FCV at startup, which resolves potential issues during server initialization and FCV changes.
SERVER-103742 - Fixed a memory corruption bug where the opWriteConcernCounters field in serverStatus could illegally embed NUL bytes. This issue caused BSON validation errors and prevented certain MongoDB binaries from correctly parsing serverStatus output, which has now been corrected.
SERVER-103841 - Fixed a memory leak in the TransactionCoordinator associated with long-lived cancellation sources. This issue caused gradual memory growth because cancellation futures related to transactions were retained indefinitely. The fix ensures that the cancellation sources are properly managed and released, resolving the memory leak.
SERVER-105478 - Fixed the issue with misbehaving replication because oplog entries from the same batch could not be applied by separating eligible and ineligible oplog entries for the applier with secondaryDelaySecs.
WT-14140 - Fixed a performance regression in WiredTiger by removing an unnecessary schema lock. This issue was caused by taking an unnecessary schema lock for active file: data handles that were not currently being swept, which could degrade performance during certain concurrent operations. The fix prevents this redundant locking, improving concurrency.
SERVER-105873 - Fixed a concurrency issue where QueryPlannerParams could hold invalid index pointers, leading to crashes during query execution. The fix ensures that the QueryPlannerParams object no longer maintains pointers to internal state owned by an IndexCatalogEntry, preventing pointer invalidation if the catalog entry is refreshed or destroyed during a yielded query operation.
SERVER-82688- Fixed an issue where the mongod process could crash if the number of incoming connections exceeded WiredTiger’s configured session_max limit. The fix ensures that the server handles a high volume of connections gracefully without crashing, improving stability and resilience under heavy load.
SERVER-95374 - Fixed the issue with compound wildcard indexes incorrectly pushing down predicates during union or planning by stripping invalid compound wildcard index assignment in rated MatchExpression tree
SERVER-103960 - Added a validation on the field path to ensure the number of parts does not exceed 255 to prevent potential issues when using excessively long field paths in the database.
SERVER-112467 - Improved connections handling by tracking and reporting the number of connections accepted on the proxy port that are pending the proxy protocol header.
SERVER-112520 - Fixed an issue with inability to write to geo index when inserting a document to timeseries existing bucket by improving index maintenance for 2dsphere indexes on timeseries collections
WT-9575 - Fixed an issue in WiredTiger where pages with updates newer than the oldest transaction ID were not being queued for eviction by allowing evicting newly updated paged

Find the full list of changes in the release notes for:

Changelog¶

New Features¶

PSMDB-1575 - Added integration with OpenBao for data-at-rest encryption

Improvements¶

PSMDB-1781 - Adjusted telemetry to report OpenBao and HashiCorp Vault usage separately
PSMDB-1135 - Added extra checks to prevent the percona-server-mongodb-enable-auth.sh from failing if keyfile is not present
PSMDB-1858 - Added official support for Rocky Linux 8 and 9
PSMDB-1830 - Excluded ProBuilds from documentation

Fixed Bugs¶

PSMDB-1155 - Fixed an issue with Percona Server for MongoDB being stuck on attempt to open backupCursorExtend for a standalone instance by reporting an error about this operation as not allowed.
PSMDB-1757 - Prevented file copy-based initial sync if the storage engine is not WiredTiger
PSMDB-1838 - Fixed high-severity vulnerabilities identified in latest Percona Server for MongoDB Docker images
PSMDB-1839 - Fixed the output display of the db.adminCommand() command to show the authorization result, aligning with upstream behavior.