From 45a1321622a271bf24dfd6133d81fd54c164d85e Mon Sep 17 00:00:00 2001 From: rasika-chivate <95711051+rasika-chivate@users.noreply.github.com> Date: Wed, 22 Jul 2026 14:32:24 +0530 Subject: [PATCH 01/41] Release Notes 8.3 --- docs/release_notes/8.0.12-4.md | 100 --------------- docs/release_notes/8.0.16-5.md | 120 ------------------ docs/release_notes/8.0.17-6.md | 77 ----------- docs/release_notes/8.0.19-7.md | 103 --------------- docs/release_notes/8.0.20-8.md | 52 -------- docs/release_notes/8.0.21-9.md | 88 ------------- docs/release_notes/8.0.23-10.md | 47 ------- docs/release_notes/8.0.26-11.md | 80 ------------ docs/release_notes/8.0.4-2.md | 40 ------ docs/release_notes/8.0.8-3.md | 94 -------------- docs/release_notes/{8.0.4-1.md => 8.3.4-1.md} | 6 +- 11 files changed, 3 insertions(+), 804 deletions(-) delete mode 100644 docs/release_notes/8.0.12-4.md delete mode 100644 docs/release_notes/8.0.16-5.md delete mode 100644 docs/release_notes/8.0.17-6.md delete mode 100644 docs/release_notes/8.0.19-7.md delete mode 100644 docs/release_notes/8.0.20-8.md delete mode 100644 docs/release_notes/8.0.21-9.md delete mode 100644 docs/release_notes/8.0.23-10.md delete mode 100644 docs/release_notes/8.0.26-11.md delete mode 100644 docs/release_notes/8.0.4-2.md delete mode 100644 docs/release_notes/8.0.8-3.md rename docs/release_notes/{8.0.4-1.md => 8.3.4-1.md} (99%) diff --git a/docs/release_notes/8.0.12-4.md b/docs/release_notes/8.0.12-4.md deleted file mode 100644 index dc3a25c69..000000000 --- a/docs/release_notes/8.0.12-4.md +++ /dev/null @@ -1,100 +0,0 @@ -title: Percona Server for MongoDB 8.0.12-4 ({{date.8_0_12}}) -summary: Learn about improvements, new features, and bug and security vulnerability fixes in this release -authors: - - Anastasia Alexandrova -version: 8.0.12-4 ---- - -# Percona Server for MongoDB {{ page.meta.version }} ({{date.8_0_12}}) - -[Install](../install/index.md){.md-button} -[Upgrade from MongoDB Community](../install/upgrade-from-mongodb.md){.md-button} - -Percona Server for MongoDB {{ page.meta.version }} 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 {{ page.meta.version }} includes the improvements and bug fixes of [MongoDB 8.0.9 Community Edition](https://www.mongodb.com/docs/manual/release-notes/8.0/#8.0.9---may-1--2025), [MongoDB 8.0.10 Community Edition](https://www.mongodb.com/docs/manual/release-notes/8.0/#8.0.10---jun-04--2025), [MongoDB 8.0.11 Community Edition](https://www.mongodb.com/docs/manual/release-notes/8.0/#8.0.11---jun-30--2025), [MongoDB 8.0.12 Community Edition](https://www.mongodb.com/docs/manual/release-notes/8.0/#8.0.12---july-23--2025). - -It also includes the fix for security vulnerability [CVE-2025-6714](https://nvd.nist.gov/vuln/detail/CVE-2025-6714) reported in [SERVER-106753](https://jira.mongodb.org/browse/SERVER-106753). - -Percona Server for MongoDB {{ page.meta.version }} supports protocols and drivers of MongoDB Community 8.0.9 through 8.0.12. - - -## Release Highlights - -This release provides the following features and improvements: - -### Boost performance during cluster restore and scaling with file copy-based initial sync - -You can now select how a newly added or a restored replica set member synchronizes the data from other members - via logical or file copy-based initial sync. File copy-based initial sync copies physical files from the source node. This sync method is faster than the logical one and it reduces your maintenance time on scaling your cluster. - - - -The performance advantage of file copy-based over logical initial sync varies based on data set characteristics. While file copy-based initial sync can be significantly quicker, its efficiency is influenced by factors such as document count, collection distribution, and indexing structure. - -This feature is available in Percona Server for MongoDB Pro out of the box. [Become a Percona Customer](https://www.percona.com/about/contact) to enjoy all Pro features with little to no effort from your side. Alternatively, you can receive it by building Percona Server from the source code. - -*Update from {{date.pro_eol}}: We no longer release Percona Server for MongoDB Pro Builds. All features included in Pro Builds are accessible for everyone in our public regular builds. If you need a Pro Build for that specific version, please contact your Percona representative for guidance. We're here to help ensure a smooth transition and continued success with Percona open-source solutions.* - - -### Enhance authentication security via a token-based authentication flow with OpenID Connect (OIDC) - -Percona Server for MongoDB now supports OpenID Connect (OIDC) / OAuth 2.0, providing a secure and simple way to manage user authentication using identity and access tokens. This feature allows you to centralize user management with a single identity provider, enhance security by eliminating the need to store credentials in your database and reduce the risk of credential theft. You can leverage enhanced authentication techniques like Single Sign-On (SSO) and Multi-Factor Authentication (MFA), improving your overall security posture and user experience. - -Learn more about OIDC connect in our [documentation](../oidc.md) - -This feature is available in [Percona Server for MongoDB Pro](../psmdb-pro.md) out of the box. You can also receive it by building Percona Server from the source code. - -### Packaging changes - -Percona Server for MongoDB {{ page.meta.version }} is no longer supported on Ubuntu 20.04 (Focal Fossa) as this operating system has reached end of life. If you're not ready to upgrade to a newer Ubuntu OS but still want to update Percona Server for MongoDB, [contact us](https://hubs.ly/Q03rRtDg0)! We're here to make your databases run better. - -### Upstream Improvements - -The bug fixes, provided by MongoDB Community Edition and included in Percona Server for MongoDB, are the following: - -* [SERVER-106753](https://jira.mongodb.org/browse/SERVER-106753) - Fixed the issue with incorrect handling of incomplete data that may prevent `mongos` from accepting new connections. The issue affects deployments configured to use a load balancer like HAProxy and affects Percona Server for MongoDB Server v6.0 prior to 6.0.23, Percona Server for MongoDB Server v7.0 prior to 7.0.20 and Percona Server for MongoDB Server v8.0 prior to 8.0.12. We recommend users to upgrade to the latest version as soon as possible. -* [SERVER-92236](https://jira.mongodb.org/browse/SERVER-92236) - Fixed an issue where servers performing chunk migrations could experience continuous memory growth caused by the cancellation mechanism for migration operations not properly releasing memory. -* [SERVER-92806](https://jira.mongodb.org/browse/SERVER-92806) - Tracked nested paths through MatchExpression trees while encoding indexability for plan cache entries -* [SERVER-96197](https://jira.mongodb.org/browse/SERVER-96197) - Fixed the issue with retrieving the wrong resolved namespace for a collection when there are multiple collections with the same name involved in a query -* [SERVER-100785](https://jira.mongodb.org/browse/SERVER-100785) - Fixed the issue with config server crashing after issuing a `reshardCollection` command with malformed `zones` by adding a validation for zone ranges -* [SERVER-105375](https://jira.mongodb.org/browse/SERVER-105375) - Resolved a bug where queries using the $elemMatch operator with an expression that could never be true would incorrectly trigger a full collection scan. The server now correctly applies an efficient plan to immediately return an empty result, which prevents unnecessary work and restores optimal query performance. -* [SERVER-106614](https://jira.mongodb.org/browse/SERVER-106614) - Fixed the issue with `mongos` router not being able to connect to a replica set shards that were added prior to MongoDB 8.0 and miss the replSetConfigVersion in the config.shards collection. The issue is fixed by matching `config.shards` entries without `replSetConfigVersion`. -* [SERVER-95523](https://jira.mongodb.org/browse/SERVER-95523) - Fixed a race condition where a concurrent `upsert` operation could incorrectly fail with a `DuplicateKey` error instead of retrying as an update. With this fix, the upsert operation now correctly retries and applies the update when another operation inserts the document in parallel. -* [SERVER-95524](https://jira.mongodb.org/browse/SERVER-95524) - Avoided retrying on duplicate key error for upserts in multi-document transactions -* [SERVER-97368](https://jira.mongodb.org/browse/SERVER-97368) - Enabled TTL deletes on time-series collections containing data prior to 1970 -* [SERVER-99342](https://jira.mongodb.org/browse/SERVER-99342) - Fixed the issue with internal metrics for throughput decreases not being correctly recorded. This issue caused inaccurate reporting of throughput changes - -Find the full list of changes in the release notes for: - -* [MongoDB 8.0.9 Community Edition](https://www.mongodb.com/docs/manual/release-notes/8.0/#8.0.9---may-1--2025), -* [MongoDB 8.0.10 Community Edition](https://www.mongodb.com/docs/manual/release-notes/8.0/#8.0.10---jun-04--2025), -* [MongoDB 8.0.11 Community Edition](https://www.mongodb.com/docs/manual/release-notes/8.0/#8.0.11---jun-30--2025), -* [MongoDB 8.0.12 Community Edition](https://www.mongodb.com/docs/manual/release-notes/8.0/#8.0.12---july-23--2025). - -## Changelog - -### New Features - -* [PSMDB-1284](https://perconadev.atlassian.net/browse/PSMDB-1284) - Add the ability to perform file copy-based initial sync -* [PSMDB-1438](https://perconadev.atlassian.net/browse/PSMDB-1438) - Add the ability to authenticate users using OpenID Connect (OIDC) - -### Improvements - -* [PSMDB-1619](https://perconadev.atlassian.net/browse/PSMDB-1619) - Make log rotation behavior compatible with MongoDB Community and MongoDB Enterprise Advanced by renaming existing log file to a name with a timestamp and starting a new one -* [PSMDB-1633](https://perconadev.atlassian.net/browse/PSMDB-1633) - Implemented 'encryptionAtRest' field in 'serverStatus()' -* [PSMDB-1634](https://perconadev.atlassian.net/browse/PSMDB-1634) - Improved the `mongod.1` manpage by adding reference to official documentation - -### Fixed Bugs - -* [PSMDB-1615](https://perconadev.atlassian.net/browse/PSMDB-1615) - Fixed the issue with corrupt/unusable debug files in RPM-based systems for Percona Server for MongoDB 6, 7 and 8 - -* [PSMDB-1679](https://perconadev.atlassian.net/browse/PSMDB-1679) - Fixed the issue with Percona Server for MongoDB not starting with custom configurations (Thank you Ilnar Gabidullin for reporting this issue) - -* [PSMDB-1712](https://perconadev.atlassian.net/browse/PSMDB-1712) - Fixed the issue with the server сrash when accessing LDAP by improving the `start_poll` function behavior - -* [PSMDB-1730](https://perconadev.atlassian.net/browse/PSMDB-1730) - Fixed the issue with LDAP authentication via SASL by adding the package `cyrus-sasl-plain` in Docker images for Percona Server for MongoDB 6, 7 and 8 - -* [PSMDB-1745](https://perconadev.atlassian.net/browse/PSMDB-1745) - Aligned the audit log rotation behavior when the server is started with the `reopen` behavior so that on startup the server keeps writing events to the same log file. - -* [PSMDB-1754](https://perconadev.atlassian.net/browse/PSMDB-1754) - Fixed the issue with log rotation behavior that was caused by replacing the rotated audit log file with a timestamp if it existed. The fix is to reopen a current audit log file in the append mode and write events there. \ No newline at end of file diff --git a/docs/release_notes/8.0.16-5.md b/docs/release_notes/8.0.16-5.md deleted file mode 100644 index 170dc74c6..000000000 --- a/docs/release_notes/8.0.16-5.md +++ /dev/null @@ -1,120 +0,0 @@ -title: Percona Server for MongoDB 8.0.16-5 ({{date.8_0_16}}) -summary: Learn about improvements, new features, and bug and security vulnerability fixes in this release -authors: - - Anastasia Alexandrova -version: 8.0.16-5 ---- - -# Percona Server for MongoDB {{ page.meta.version }} ({{date.8_0_16}}) - -[Install](../install/index.md){.md-button} -[Upgrade from MongoDB Community](../install/upgrade-from-mongodb.md){.md-button} - -Percona Server for MongoDB {{ page.meta.version }} 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 {{ page.meta.version }} includes the improvements and bug fixes of the following versions of MongoDB Community Edition: - -* [MongoDB 8.0.13 Community Edition](https://www.mongodb.com/docs/manual/release-notes/8.0/#8.0.13---aug-21--2025) -* [MongoDB 8.0.14 Community Edition](https://www.mongodb.com/docs/manual/release-notes/8.0/#8.0.14---sep-25--2025) -* [MongoDB 8.0.15 Community Edition](https://www.mongodb.com/docs/manual/release-notes/8.0/#8.0.15---oct-2--2025) -* [MongoDB 8.0.16 Community Edition](https://www.mongodb.com/docs/manual/release-notes/8.0/#8.0.16---nov-21--2025) - -Percona Server for MongoDB {{ page.meta.version }} 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](../openbao.md). - -### 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](https://jira.mongodb.org/browse/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](https://jira.mongodb.org/browse/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](https://jira.mongodb.org/browse/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](https://jira.mongodb.org/browse/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](https://jira.mongodb.org/browse/SERVER-102670) - Fixed an issue that caused incorrect error handling during ordered time-series inserts by clearing errors before retrying. - -* [SERVER-107361](https://jira.mongodb.org/browse/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](https://github.com/mongodb/support-tools/tree/master/timeseries-mixed-schema) for a complete step-by-step guide on how to resolve the impacted collections. - -* [SERVER-100448](https://jira.mongodb.org/browse/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](https://jira.mongodb.org/browse/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](https://jira.mongodb.org/browse/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](https://jira.mongodb.org/browse/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](https://jira.mongodb.org/browse/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](https://jira.mongodb.org/browse/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](https://jira.mongodb.org/browse/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](https://jira.mongodb.org/browse/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](https://jira.mongodb.org/browse/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](https://jira.mongodb.org/browse/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](https://jira.mongodb.org/browse/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](https://jira.mongodb.org/browse/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: - -* [MongoDB 8.0.13 Community Edition](https://www.mongodb.com/docs/manual/release-notes/8.0/#8.0.13---aug-21--2025) -* [MongoDB 8.0.14 Community Edition](https://www.mongodb.com/docs/manual/release-notes/8.0/#8.0.14---sep-25--2025) -* [MongoDB 8.0.15 Community Edition](https://www.mongodb.com/docs/manual/release-notes/8.0/#8.0.15---oct-2--2025) -* [MongoDB 8.0.16 Community Edition](https://www.mongodb.com/docs/manual/release-notes/8.0/#8.0.16---nov-21--2025) - -## Changelog - -### New Features - -* [PSMDB-1575](https://perconadev.atlassian.net/browse/PSMDB-1575) - Added integration with OpenBao for data-at-rest encryption - -### Improvements - -* [PSMDB-1781](https://perconadev.atlassian.net/browse/PSMDB-1781) - Adjusted telemetry to report OpenBao and HashiCorp Vault usage separately - -* [PSMDB-1135](https://perconadev.atlassian.net/browse/PSMDB-1135) - Added extra checks to prevent the `percona-server-mongodb-enable-auth.sh` from failing if keyfile is not present - -* [PSMDB-1858](https://perconadev.atlassian.net/browse/PSMDB-1858) - Added official support for Rocky Linux 8 and 9 - -* [PSMDB-1830](https://perconadev.atlassian.net/browse/PSMDB-1830) - Excluded ProBuilds from documentation - -### Fixed Bugs - -* [PSMDB-1155](https://perconadev.atlassian.net/browse/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](https://perconadev.atlassian.net/browse/PSMDB-1757) - Prevented file copy-based initial sync if the storage engine is not WiredTiger - -* [PSMDB-1838](https://perconadev.atlassian.net/browse/PSMDB-1838) - Fixed high-severity vulnerabilities identified in latest Percona Server for MongoDB Docker images - -* [PSMDB-1839](https://perconadev.atlassian.net/browse/PSMDB-1839) - Fixed the output display of the `db.adminCommand()` command to show the authorization result, aligning with upstream behavior. - diff --git a/docs/release_notes/8.0.17-6.md b/docs/release_notes/8.0.17-6.md deleted file mode 100644 index dac2d7c0b..000000000 --- a/docs/release_notes/8.0.17-6.md +++ /dev/null @@ -1,77 +0,0 @@ -title: Percona Server for MongoDB 8.0.17-6 ({{date.8_0_17}}) -summary: Learn about improvements, new features, and bug and security vulnerability fixes in this release -authors: - - Anastasia Alexandrova -version: 8.0.17-6 ---- - -# Percona Server for MongoDB {{ page.meta.version }} ({{date.8_0_17}}) - -[Install](../install/index.md){.md-button} -[Upgrade from MongoDB Community](../install/upgrade-from-mongodb.md){.md-button} - -Percona Server for MongoDB {{ page.meta.version }} 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 {{ page.meta.version }} includes the improvements and bug fixes of [MongoDB 8.0.17 Community Edition](https://www.mongodb.com/docs/manual/release-notes/8.0/#8.0.17---dec-19--2025) - - -Percona Server for MongoDB {{ page.meta.version }} supports protocols and drivers of MongoDB Community 8.0.17. - - -## Security update: Mitigation of heap memory disclosure vulnerability - -This release fixes security vulnerability [CVE-2025-14847: CWE-130](https://radar.offseq.com/threat/cve-2025-14847-cwe-130-improper-handling-of-length-dd0a4a45) in how MongoDB uses `zlib` compression library. Attackers with network access to `mongod` or `mongos` can extract fragments of uninitialized server memory without authentication if zlib compression is enabled. This memory may contain sensitive data, which poses a serious information disclosure risk. - -### Affected versions - -This vulnerability affects the following versions of MongoDB Community Edition and Percona Server for MongoDB: - -* Percona Server for MongoDB 8.0.4-1 through 8.0.16-5 -* Percona Server for MongoDB 7.0.2-1 through 7.0.26-14 -* Percona Server for MongoDB 6.0.2-1 through 6.0.25-20 -* Percona Server for MongoDB 5.0.2-1 through 5.0.29-25 -* Percona Server for MongoDB 4.4.0-1 through 4.4.29-28 -* All Percona Server for MongoDB Server 4.2 versions -* All Percona Server for MongoDB Server 4.0 versions -* All Percona Server for MongoDB Server 3.6 versions - -The issue is fixed upstream and is included in Percona Server for MongoDB 7.0.28-15 and 8.0.17-6. We strongly recommend upgrading Percona Server for MongoDB to this latest minor version to ensure your deployments remain secure. - -### Workaround - -If upgrading is not possible right away, disable `zlib` compression by configuring `networkMessageCompressors` (or `net.compression.compressors`) in configuration or startup parameters. Safe alternatives are `snappy` or `zstd`. - -=== "via Configuration File" - - To disable `zlib` compression, edit the `mongod.conf` or `mongos.conf` configuration file and set the `net.compression.compressors` parameter as follows: - - ```yaml - net: - compression: - compressors: snappy,zstd - ``` - - Then restart the `mongod` or `mongos` service to apply the changes. - -=== "via Command Line" - - To disable `zlib` compression, start `mongod` or `mongos` with the `--networkMessageCompressors` parameter as follows: - - ```bash - mongod --networkMessageCompressors snappy,zstd - ``` - - Or for `mongos`: - - ```bash - mongos --networkMessageCompressors snappy,zstd - ``` - -Verify that `zlib` is disabled using the `db.adminCommand({ getCmdLineOpts: 1 })`. Ensure logs show no zlib negotiation when you try to connect to the server with a client that explicitly requests `zlib`. - - -### Upstream Improvements - -* [SERVER-115508](https://jira.mongodb.org/browse/SERVER-115508) - Fixed a critical security vulnerability (CVE-2025-14847) where unauthenticated remote attackers could read uninitialized heap memory via the zlib compression protocol. This was caused by improper handling of length parameter inconsistencies in zlib-compressed protocol headers. The fix ensures the server uses minimally sized buffers for uncompressed messages, preventing sensitive information disclosure. - diff --git a/docs/release_notes/8.0.19-7.md b/docs/release_notes/8.0.19-7.md deleted file mode 100644 index fe2aefb76..000000000 --- a/docs/release_notes/8.0.19-7.md +++ /dev/null @@ -1,103 +0,0 @@ -title: Percona Server for MongoDB 8.0.19-7 ({{date.8_0_19}}) -summary: Learn about improvements, new features, and bug and security vulnerability fixes in this release -authors: - - Rasika Chivate -version: 8.0.19-7 ---- - -# Percona Server for MongoDB {{ page.meta.version }} ({{date.8_0_19}}) - -[Install](../install/index.md){.md-button} -[Upgrade from MongoDB Community](../install/upgrade-from-mongodb.md){.md-button} - -Percona Server for MongoDB {{ page.meta.version }} 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 {{ page.meta.version }} includes the improvements and bug fixes from: - -- [MongoDB 8.0.18 Community Edition](https://www.mongodb.com/docs/manual/release-notes/8.0/#8.0.18---jan-27--2026) - -- [MongoDB 8.0.19 Community Edition](https://www.mongodb.com/docs/manual/release-notes/8.0/#8.0.19---feb-10--2026) - -Percona Server for MongoDB {{ page.meta.version }} supports protocols and drivers of MongoDB Community **8.0.18** and **8.0.19**. - -## New feature - -- [PSMDB-1893](https://perconadev.atlassian.net/browse/PSMDB-1893): -**Disable specific FTDC metric groups** - - Percona Server for MongoDB now permits administrators to disable specific diagnostic metric groups via two new server parameters: - - - **diagnosticDataCollectionEnableSystemMetricsDisks** - - Enables or disables collection of disk-level statistics. - - Type: Boolean (`true`/`false`) - - Default: true (enabled) - - Scope: Startup; runtime configurable via `setParameter` - - - **diagnosticDataCollectionEnableSystemMetricsMounts** - - Enables or disables collection of mount-level statistics. - - Type: Boolean (true/false) - - Default: true (enabled) - - Scope: Startup; runtime configurable via setParameter - - Database administrators can avoid delays in diagnostics caused by unstable or unresponsive mount points in NFS, FUSE, or autofs environments by excluding certain problematic groups like `systemMetrics`, `serverStatus.connections`, and `replSetGetStatus`. This way, the Full Time Diagnostic Data Capture (FTDC) can still deliver important insights into database performance, such as query efficiency and replication, without being hindered by system-level issues. - -Ready to explore this topic further? Check out our in-depth [documentation](https://docs.percona.com/percona-server-for-mongodb/8.0/set-parameter.html). - -## Security updates: CVE fixes from upstream MongoDB - -This release includes upstream MongoDB security fixes for the following vulnerabilities: - -### High severity - -- [SERVER-116210](https://jira.mongodb.org/browse/SERVER-116210) -**(CVE-2026-25611):** Fixed an issue where a series of specifically crafted, unauthenticated messages could exhaust available system memory, leading to a server crash. - - -- [SERVER-114838](https://jira.mongodb.org/browse/SERVER-114838) - **(CVE-2026-25612):** Resolved a bug in the internal locking mechanism where specific resource encodings could cause unintended collisions between collections. This could lead to resource unavailability due to conflicting locks. - -- [SERVER-113685](https://jira.mongodb.org/browse/SERVER-113685) - **(CVE-2026-25613):** Fixed a vulnerability where an authorized user could crash the server by querying a collection containing an invalid compound wildcard index. - -- [SERVER-102364](https://jira.mongodb.org/browse/SERVER-102364) - **(CVE-2026-1849):** Addressed an Out-Of-Memory (OOM) failure during the evaluation of expressions that produce deeply nested documents. The server now properly validates recursion depth to prevent unchecked memory consumption. - -- [SERVER-114126](https://jira.mongodb.org/browse/SERVER-114126) - **(CVE-2026-1850):** Fixed an issue where complex boolean expression simplifications within the Query Planner by an authorized user could lead to excessive memory usage and an OOM crash. - -- [SERVER-99119](https://jira.mongodb.org/browse/SERVER-99119) **(CVE-2026-25610):** Resolved a vulnerability where an authorized user could trigger a server crash by executing a `$geoNear` aggregation pipeline with specific invalid index hints. - -- [SERVER-114695](https://jira.mongodb.org/browse/SERVER-114695) - **(CVE-2026-1848):** Resolved a vulnerability where connections received on the proxy port (pending proxy protocol headers) were excluded from the `maxConns` limit. This flaw exposed the server to resource exhaustion and OOM (Out-of-Memory) crashes during high-traffic bursts. - -- [SERVER-113532](https://jira.mongodb.org/browse/SERVER-113532) - **(CVE-2026-1847):** Resolved an issue where inserting specific large documents could prevent secondaries from fetching the oplog from the primary. This could stall replication and potentially lead to node instability. - -### Medium severity - -- [SERVER-112952](https://jira.mongodb.org/browse/SERVER-112952) - **(CVE-2026-25609):** Corrected an issue where improper validation of the profile command caused requests altering the `filter` to be incorrectly treated as read-only. - - -### Affected versions - -These vulnerabilities affect the following versions of MongoDB Community Edition and Percona Server for MongoDB: - -- All Percona Server for MongoDB 8.0.x versions -- MongoDB Community 8.0 versions prior to 8.0.18 - - -These issues are fixed in the upstream MongoDB 8.0 patch line and are included in **Percona Server for MongoDB 8.0.19-7**. We strongly recommend upgrading to **8.0.19-7** to ensure your deployments include the latest security fixes. - -## Tools packaged with this release - -Percona Server for MongoDB packages the following MongoDB tools: - -- MongoDB Shell (mongosh): 2.6.0 — [upstream changelog :octicons-link-external-16:](https://www.mongodb.com/docs/mongodb-shell/changelog/){:target="_blank"} - -- MongoDB Database Tools: 100.14.1 — [upstream release notes :octicons-link-external-16:](https://www.mongodb.com/docs/database-tools/release-notes/database-tools-changelog/){:target="_blank"} - -## Bugs fixed - -- [PSMDB-1922](https://perconadev.atlassian.net/browse/PSMDB-1922): Resolved an issue where the `auditGetOptions` command could be executed by users with any privilege level. Access is now strictly restricted to users with **admin privileges**, aligning its security requirements with the `getParameter` command to prevent unauthorized access to audit configuration options. diff --git a/docs/release_notes/8.0.20-8.md b/docs/release_notes/8.0.20-8.md deleted file mode 100644 index 9fcda51e8..000000000 --- a/docs/release_notes/8.0.20-8.md +++ /dev/null @@ -1,52 +0,0 @@ -title: Percona Server for MongoDB 8.0.20-8 ({{date.8_0_20}}) -summary: Learn about improvements, new features, and bug and security vulnerability fixes in this release -authors: - - Rasika Chivate -version: 8.0.20-8 ---- - -# Percona Server for MongoDB {{ page.meta.version }} ({{date.8_0_20}}) - -[Install](../install/index.md){.md-button} -[Upgrade from MongoDB Community](../install/upgrade-from-mongodb.md){.md-button} - -Percona Server for MongoDB {{ page.meta.version }} 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 {{ page.meta.version }} includes the improvements and bug fixes from: - -- [MongoDB 8.0.20 Community Edition](https://www.mongodb.com/docs/manual/release-notes/8.0/#8.0.20---mar-17--2026) - - -Percona Server for MongoDB {{ page.meta.version }} supports protocols and drivers of MongoDB Community **8.0.20**. - - -## Release highlights - -### Enhanced LDAP authentication caching - -To provide better parity with MongoDB Enterprise and improve performance in high-scale environments, we have introduced two new configuration parameters for LDAP user caching. These options allow administrators to fine-tune how and when cached user information is refreshed, reducing unnecessary overhead on LDAP servers while ensuring security data remains current. - -**New parameters** - -**ldapUserCacheRefreshInterval:** The `ldapUserCacheRefreshInterval` parameter sets the frequency (in seconds) at which the server proactively refreshes cached user information from the LDAP server. This allows the system to update permissions and group memberships in the background before the cache entry expires. For more detailed information, refer to [MongoDB server parameters](https://www.mongodb.com/docs/manual/reference/parameters/#mongodb-parameter-param.ldapUserCacheRefreshInterval). - -**ldapShouldRefreshUserCacheEntries:** The `ldapShouldRefreshUserCacheEntries` parameter is a toggle that determines the cache renewal strategy. For more detailed information, refer to [MongoDB server parameters](https://www.mongodb.com/docs/manual/reference/parameters/#mongodb-parameter-param.ldapShouldRefreshUserCacheEntries). - - - - If set to true: The server will use the `ldapUserCacheRefreshInterval` to proactively update entries. - - - If set to false: The server will wait for the `ldapUserCacheInvalidationInterval` (already supported in PSMDB) to pass before clearing and refetching the entry on the next login attempt. - - -## Changelog - -### Improvements - -[PSMDB-1947](https://perconadev.atlassian.net/browse/PSMDB-1947): To provide better parity with MongoDB Enterprise and improve performance in high-scale environments, we have introduced two new configuration parameters for LDAP user caching. These options allow administrators to fine-tune how and when cached user information is refreshed, reducing unnecessary overhead on LDAP servers while ensuring security data remains current. - -### Bugs - -[PSMDB-1998](https://perconadev.atlassian.net/browse/PSMDB-1998): Resolved an issue where user authentication was stuck indefinitely when the LDAP server was unreachable. Timeouts are now applied to LDAP connections to avoid blocking and ensure more reliable authentication. - - diff --git a/docs/release_notes/8.0.21-9.md b/docs/release_notes/8.0.21-9.md deleted file mode 100644 index 8916dd14d..000000000 --- a/docs/release_notes/8.0.21-9.md +++ /dev/null @@ -1,88 +0,0 @@ -# Percona Server for MongoDB 8.0.21-9 ({{date.8_0_21}}) - -[Installation](../install/index.md){.md-button} -[Upgrade from MongoDB Community](../install/upgrade-from-mongodb.md){.md-button} - -!!! tip "Release notes updated" - CVE-2026-8843 has been added on **2026-05-18**. - -Percona Server for MongoDB 8.0.21-9 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.21-9** includes the improvements and bug fixes of: - -- [MongoDB 8.0.21 Community Edition :octicons-link-external-16:](https://www.mongodb.com/docs/manual/release-notes/8.0/#8.0.21---upcoming){:target="_blank"} - - -It supports protocols and drivers of MongoDB Community **8.0.21**. - -!!! warning "Amazon Linux 2023 users" - Percona Server for MongoDB 8.0.21-9 now requires **OpenSSL 3.4.0 or higher**. To ensure a successful installation or upgrade on Amazon Linux 2023, verify that your environment meets this minimum requirement. - - - If your current system version is below 3.4.0, **update the OpenSSL package** or **upgrade your operating system** to a release that includes the required OpenSSL version. - - This version of Percona Server for MongoDB will not install or run correctly without **OpenSSL 3.4.0+** available in the system path. - - -## Release highlights - -### LDAP userToDNMapping cache - -Starting with PSMDB 8.0.21-9, we have implemented caching of **LDAP userToDNMapping** to reduce the number of round-trips to the LDAP server during authentication and authorization. Caching is controlled by `security.ldap.userToDNMapping` (exposed as `--ldapUserToDNMapping` at startup and `ldapUserToDNMapping` at runtime). - -The following server parameters control the cache: - -- `ldapUserToDNCacheTTLSeconds`: Specifies how long (in seconds) a cache entry remains valid. - - Default: `30` - - Set to `0` to turn off caching. - - -- `ldapUserToDNCacheSize`: Defines the maximum number of entries stored in the cache. - - Default: `10000` - - Set to `0` to turn off caching. - -For more information about this feature, refer to our [documentation](https://docs.percona.com/percona-server-for-mongodb/8.0/ldap-parameters.html). - -## Changelog - -### New feature - -- [PSMDB-2003](https://perconadev.atlassian.net/browse/PSMDB-2003): We have implemented caching of **LDAP userToDNMapping** to reduce the number of round-trips to the LDAP server during authentication and authorization. Caching is controlled by `security.ldap.userToDNMapping` (exposed as `--ldapUserToDNMapping` at startup and `ldapUserToDNMapping` at runtime). - -## Security updates: CVE fixes from upstream MongoDB - -This release includes upstream MongoDB security fixes for the following vulnerabilities: - -### High severity - -- [SERVER-116327 :octicons-link-external-16:](https://jira.mongodb.org/browse/SERVER-116327){:target="_blank"} **(CVE-2026-8843)**: Fixed a vulnerability where creating `2dsphere_bucket` or `queryable_encrypted_range` indexes on unsupported collection types appeared to succeed but caused `mongod` to crash on the next `insert` that updated those indexes. An authenticated user with **index creation privileges** could exploit this to cause a denial of service. These conditions are now enforced prior to index creation, which prevents the creation of invalid indexes and eliminates server crashes during both index creation and subsequent inserts. - -- [SERVER-119981](https://jira.mongodb.org/browse/SERVER-119981) **(CVE-2026-6914)**: Fixed an issue where computing the MD5 checksum of a specifically malformed `BSON` object under certain conditions could cause the MongoDB server to crash, resulting in temporary loss of availability. - -### Medium severity - -- [SERVER-119679](https://jira.mongodb.org/browse/SERVER-119679) **(CVE-2026-6915)**: Resolved an issue where an authorization flaw in the user management command allowed authenticated users to make limited changes to authentication-related data associated with another user's account. This issue could potentially affect how authentication was performed for the impacted account. - - -### Affected versions - -These vulnerabilities affect the following versions of MongoDB Community Edition and Percona Server for MongoDB: - -- All Percona Server for MongoDB 8.0.x versions -- MongoDB Community 8.0 versions prior to 8.0.21 - -## Security fixes: CVEs addressed in Percona Server for MongoDB Docker images - -We have identified and **fixed** the following security vulnerabilities (CVEs) in [Percona Server for MongoDB Docker images :octicons-link-external-16:](https://hub.docker.com/r/percona/percona-server-mongodb). These issues have been addressed and are resolved in the **latest release**. - -- [CVE-2026-4424](https://access.redhat.com/security/cve/cve-2026-4424) -- [CVE-2026-27135](https://access.redhat.com/security/cve/cve-2026-27135) -- [CVE-2026-32281](https://access.redhat.com/security/cve/cve-2026-32281) -- [CVE-2026-33810](https://access.redhat.com/security/cve/cve-2026-33810) - - -## Tools packaged with this release - -Percona Server for MongoDB packages the following MongoDB tools: - -- MongoDB Shell (mongosh): 2.8.2 — [upstream release notes :octicons-link-external-16:](https://www.mongodb.com/docs/mongodb-shell/changelog/#v2.8.2){:target="_blank"} - diff --git a/docs/release_notes/8.0.23-10.md b/docs/release_notes/8.0.23-10.md deleted file mode 100644 index 7ae549621..000000000 --- a/docs/release_notes/8.0.23-10.md +++ /dev/null @@ -1,47 +0,0 @@ ---- -title: "Percona Server for MongoDB 8.0.23-10 (2026-05-21)" -summary: Learn about security vulnerabilities and bug fixes in this release -authors: - - Rasika Chivate -version: 8.0.23-10 ---- - -# Percona Server for MongoDB {{ page.meta.version }} ({{date.8_0_23}}) - -[Installation](../install/index.md){.md-button} -[Upgrade from MongoDB Community](../install/upgrade-from-mongodb.md){.md-button} - -Percona Server for MongoDB {{ page.meta.version }} 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 **{{ page.meta.version }}** includes the improvements and bug fixes of: - -- [MongoDB 8.0.23 Community Edition :octicons-link-external-16:](https://www.mongodb.com/docs/manual/release-notes/8.0/#8.0.23---may-12--2026){:target="_blank"} - -- Supports protocols and drivers of MongoDB Community **8.0.23**. - - -## Security updates: CVE fixes from upstream MongoDB - -This release includes upstream MongoDB security fixes for the following vulnerabilities: - -### High severity - -- [SERVER-126021 :octicons-link-external-16:](https://jira.mongodb.org/browse/SERVER-126021){:target="_blank"} **(CVE-2026-8053):** A vulnerability in the time-series collection implementation allows an authenticated user with write privileges to trigger an out-of-bounds memory write in the `mongod` process. Under certain conditions, this can lead to arbitrary code execution. - -- [SERVER-122449 :octicons-link-external-16:](https://jira.mongodb.org/browse/SERVER-122449){:target="_blank"} **(CVE-2026-8199):** A vulnerability in AST processing allows an authenticated user to cause excessive memory consumption using the following operators: `$bitsAllSet`, `$bitsAnySet`, `$bitsAllClear`, `$bitsAnyClear`. This can trigger out-of-memory (OOM) conditions and service unavailability. - -- [SERVER-121610 :octicons-link-external-16:](https://jira.mongodb.org/browse/SERVER-121610){:target="_blank"} **(CVE-2026-8336):** A vulnerability in server-side JavaScript execution allows an authenticated user to crash the `mongod` process through specially crafted use of `$_internalJsEmit`, or by manipulating the `mapReduce` map function in combination with `$where`, `$function`, or the `mapReduce` reduce stage. - -### Medium severity - -- [SERVER-120668 :octicons-link-external-16:](https://jira.mongodb.org/browse/SERVER-120668){:target="_blank"} **(CVE-2026-8202):** A vulnerability in the `$trim`, `$ltrim`, and `$rtrim` aggregation operators allows an authenticated user with aggregation privileges to supply specially crafted inputs that cause excessive CPU consumption, degrading database performance and availability. - -- [SERVER-121895 :octicons-link-external-16:](https://jira.mongodb.org/browse/SERVER-121895){:target="_blank"} **(CVE-2026-8200):** A vulnerability in schema validation error handling causes unredacted user data to be written to local server log files when `insert` or `update` operations violate schema validation rules. - -## Tools packaged with this release - -| **Tool** | **Version** | **Release notes** | -|---|---|---| -| MongoDB Shell (`mongosh`) | 2.8.3 | [upstream release notes :octicons-link-external-16:](https://www.mongodb.com/docs/mongodb-shell/changelog/#v2.8.3){:target="_blank"} | -| Mongo Tools | 100.17.0 | [upstream release notes :octicons-link-external-16:](https://www.mongodb.com/docs/database-tools/release-notes/dbtools-100.17.0-changelog/){:target="_blank"} | - diff --git a/docs/release_notes/8.0.26-11.md b/docs/release_notes/8.0.26-11.md deleted file mode 100644 index 0743fa596..000000000 --- a/docs/release_notes/8.0.26-11.md +++ /dev/null @@ -1,80 +0,0 @@ ---- -version: 8.0.26-11 ---- - -# Percona Server for MongoDB {{ page.meta.version }} ({{date.8_0_26}}) - -[Installation](../install/index.md){.md-button} -[Upgrade from MongoDB Community](../install/upgrade-from-mongodb.md){.md-button} - -Percona Server for MongoDB {{ page.meta.version }} 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 **{{ page.meta.version }}** includes the improvements and bug fixes of: - -- [MongoDB 8.0.26 Community Edition :octicons-link-external-16:](https://www.mongodb.com/docs/manual/release-notes/8.0/#8.0.26---june-11--2026){:target="_blank"}, [MongoDB 8.0.25 Community Edition :octicons-link-external-16:](https://www.mongodb.com/docs/manual/release-notes/8.0/#8.0.25---june-10--2026){:target="_blank"}, and [MongoDB 8.0.24 Community Edition :octicons-link-external-16:](https://www.mongodb.com/docs/manual/release-notes/8.0/#8.0.24---june-9--2026){:target="_blank"}. - -- Supports protocols and drivers of MongoDB Community **8.0.26**. - -## Upgrade recommendation - -This release contains multiple high-severity security fixes affecting all Percona Server for MongoDB 8.0.x versions. We strongly recommend **upgrading to version {{ page.meta.version }}** as soon as possible. - -## Improvements - -- [PSMDB-2038](https://perconadev.atlassian.net/browse/PSMDB-2038): Percona Server for MongoDB now exposes LDAP `userToDN` cache statistics through the `serverStatus` command. These metrics provide visibility into cache utilization and effectiveness, helping administrators troubleshoot LDAP authentication latency, validate cache behavior after configuration changes, and optimize cache sizing for their workloads. The new `ldap.userToDNCache` section reports runtime information such as cache usage, hits, misses, and invalidations, making LDAP authentication performance easier to monitor and tune. - -- [PSMDB-2071](https://perconadev.atlassian.net/browse/PSMDB-2071): Enhanced oplog record parsing to better handle legacy oplog entries that may be present after upgrades from older major versions. This improvement increases compatibility with upgraded deployments by correctly processing oplog records that contain fields no longer used in current releases. - -## Bugs fixed - -- [PSMDB-1977](https://perconadev.atlassian.net/browse/PSMDB-1977): Resolved an issue where Docker-based MongoDB instances could fail to start when replication settings were defined in `mongod.conf`. - -## Security updates - -### Affected versions - -These vulnerabilities affect the following versions: - -- All Percona Server for MongoDB 8.0.x versions - -### High severity - -- [SERVER-128125 :octicons-link-external-16:](https://jira.mongodb.org/browse/SERVER-128125){:target="_blank"} **(CVE-2026-11933):** A **use-after-free** vulnerability was identified in MongoDB Server’s server-side JavaScript engine when converting `BSON` documents to JavaScript arrays. An authenticated user with read privileges who can execute server-side JavaScript (e.g., via `$where` or `$function`) may trigger access to freed memory, which could result in information disclosure from the `mongod` process memory or a denial of service through a server crash. - -- [SERVER-125063 :octicons-link-external-16:](https://jira.mongodb.org/browse/SERVER-125063){:target="_blank"} **(CVE-2026-9740):** A vulnerability in the `BSON` validator allows an unauthenticated user to supply specially crafted input that could cause the `mongod` process to terminate unexpectedly, resulting in a denial-of-service condition. - -- [SERVER-123688 :octicons-link-external-16:](https://jira.mongodb.org/browse/SERVER-123688){:target="_blank"} **(CVE-2026-9743):** A vulnerability in the aggregation framework could allow an authenticated user with permission to run aggregation pipelines to cause a denial of service. By submitting a specially crafted aggregation query followed by additional requests on the same cursor, an attacker could cause the server process to terminate unexpectedly. - -- [SERVER-124959 :octicons-link-external-16:](https://jira.mongodb.org/browse/SERVER-124959){:target="_blank"} **(CVE-2026-9753):** A vulnerability in the `$_internalApplyOplogUpdate` aggregation stage allows an authenticated user to supply specially crafted input that could cause the server process to terminate unexpectedly. - -- [SERVER-123440 :octicons-link-external-16:](https://jira.mongodb.org/browse/SERVER-123440){:target="_blank"} **(CVE-2026-9752):** Inserting specially crafted documents into a collection with a `2dsphere` index could cause the `mongod` process to terminate unexpectedly, leading to a server crash. - -- [SERVER-123633 :octicons-link-external-16:](https://jira.mongodb.org/browse/SERVER-123633){:target="_blank"} **(CVE-2026-9750):** A vulnerability in query execution allows an authenticated user to create specially crafted documents that interfere with internal metadata processing. This can cause the server process to terminate unexpectedly and may result in incorrect query results. - -- [SERVER-124031 :octicons-link-external-16:](https://jira.mongodb.org/browse/SERVER-124031){:target="_blank"} **(CVE-2026-9749):** Aggregation pipelines that use the internal `$exchange` stage with key-range partitioning can trigger an unexpected condition when processing large numbers of documents for a single key range. This can cause the server process to terminate unexpectedly. - -- [SERVER-123951 :octicons-link-external-16:](https://jira.mongodb.org/browse/SERVER-123951){:target="_blank"} **(CVE-2026-9748):** Under specific conditions, using the internal `$_internalConvertBucketIndexStats` stage together with `$facet` can cause the `mongod` process to terminate unexpectedly. - -- [SERVER-123918 :octicons-link-external-16:](https://jira.mongodb.org/browse/SERVER-123918){:target="_blank"} **(CVE-2026-9747):** A vulnerability triggered by using `fromRouter: true` together with `runtimeConstants.userRoles` can cause the `mongod` process to terminate unexpectedly. - -- [SERVER-124190 :octicons-link-external-16:](https://jira.mongodb.org/browse/SERVER-124190){:target="_blank"} **(CVE-2026-9746):** A vulnerability in the use of `$changeStream`, `$_requestReshardingResumeToken`, and the exchange option can cause the `mongod` process to terminate unexpectedly. An authenticated user can trigger this behavior without requiring any special privileges. - -### Medium severity - -- [SERVER-123370 :octicons-link-external-16:](https://jira.mongodb.org/browse/SERVER-123370){:target="_blank"} **(CVE-2026-9751):** Percona Server for MongoDB no longer logs sensitive parameter values when they are modified using the runtime `setParameter` command. Previously, parameters such as `ldapQueryPassword` could be written to `mongod.log` in plain text, potentially exposing credentials. - - This applies to all `setParameter` operations. Parameters marked as sensitive are automatically redacted from log output, and values associated with unrecognized parameter names are also redacted to prevent accidental exposure caused by typographical errors. - -## Tools packaged with this release - -Percona repackages the upstream MongoDB Shell (`mongosh`) as `percona-mongodb-mongosh`, updating all copyright, authorship, and branding under the full product name "Percona MongoDB Shell." - -Percona also repackages and patches Mongo Tools. In this release, we've updated embedded Go libraries in the `mongodump` binary to address 15 security (severity from medium to critical) vulnerabilities: - -- `golang.org/x/crypto` updated from **v0.45.0** to **v0.52.0** — fixes [CVE-2026-39827 :octicons-link-external-16:](https://nvd.nist.gov/vuln/detail/CVE-2026-39827){:target="_blank"}, [CVE-2026-39828 :octicons-link-external-16:](https://nvd.nist.gov/vuln/detail/CVE-2026-39828){:target="_blank"}, [CVE-2026-39829 :octicons-link-external-16:](https://nvd.nist.gov/vuln/detail/CVE-2026-39829){:target="_blank"}, [CVE-2026-39830 :octicons-link-external-16:](https://nvd.nist.gov/vuln/detail/CVE-2026-39830){:target="_blank"}, [CVE-2026-39835 :octicons-link-external-16:](https://nvd.nist.gov/vuln/detail/CVE-2026-39835){:target="_blank"}, [CVE-2026-42508 :octicons-link-external-16:](https://nvd.nist.gov/vuln/detail/CVE-2026-42508){:target="_blank"}, [CVE-2026-46595 :octicons-link-external-16:](https://nvd.nist.gov/vuln/detail/CVE-2026-46595){:target="_blank"}, [CVE-2026-46597 :octicons-link-external-16:](https://nvd.nist.gov/vuln/detail/CVE-2026-46597){:target="_blank"} -- `golang.org/x/net` updated from **v0.47.0** to **v0.55.0** — fixes [CVE-2026-25680 :octicons-link-external-16:](https://nvd.nist.gov/vuln/detail/CVE-2026-25680){:target="_blank"}, [CVE-2026-25681 :octicons-link-external-16:](https://nvd.nist.gov/vuln/detail/CVE-2026-25681){:target="_blank"}, [CVE-2026-27136 :octicons-link-external-16:](https://nvd.nist.gov/vuln/detail/CVE-2026-27136){:target="_blank"}, [CVE-2026-33814 :octicons-link-external-16:](https://nvd.nist.gov/vuln/detail/CVE-2026-33814){:target="_blank"}, [CVE-2026-39821 :octicons-link-external-16:](https://nvd.nist.gov/vuln/detail/CVE-2026-39821){:target="_blank"}, [CVE-2026-42502 :octicons-link-external-16:](https://nvd.nist.gov/vuln/detail/CVE-2026-42502){:target="_blank"}, [CVE-2026-42506 :octicons-link-external-16:](https://nvd.nist.gov/vuln/detail/CVE-2026-42506){:target="_blank"} - -| **Tool** | **Base version** | **Release notes** | -|---|---|---| -| MongoDB Shell (`mongosh`) | 2.8.3 | [upstream release notes :octicons-link-external-16:](https://www.mongodb.com/docs/mongodb-shell/changelog/#v2.8.3){:target="_blank"} | -| Mongo Tools | 100.17.0 | [upstream release notes :octicons-link-external-16:](https://www.mongodb.com/docs/database-tools/release-notes/dbtools-100.17.0-changelog/){:target="_blank"} | diff --git a/docs/release_notes/8.0.4-2.md b/docs/release_notes/8.0.4-2.md deleted file mode 100644 index 4f3d9c31e..000000000 --- a/docs/release_notes/8.0.4-2.md +++ /dev/null @@ -1,40 +0,0 @@ -title: Percona Server for MongoDB 8.0.4-2 ({{date.8_0_4_2}}) -summary: Learn about improvements, new features, and bug and security vulnerability fixes in this release -authors: - - Anastasia Alexandrova -version: 8.0.4-2 ---- - -# Percona Server for MongoDB {{ page.meta.version }} ({{date.8_0_4_2}}) - -[Installation](../install/index.md){.md-button} -[Upgrade from MongoDB Community](../install/upgrade-from-mongodb.md){.md-button} - -Percona Server for MongoDB {{ page.meta.version }} 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 {{ page.meta.version }} includes the improvements and bug fixes of [MongoDB 8.0.4 Community Edition](https://www.mongodb.com/docs/manual/release-notes/8.0/#8.0.4---dec-9--2024) and supports its protocols and drivers. - - -## Release Highlights - -This release provides the following features and improvements: - -### Improved security for Docker images - -Percona Server for MongoDB Docker image is now based on Universal Base Image (UBI) version 9, which includes the latest security fixes. This makes the image compliant with the Red Hat certification and ensures the seamless work of containers on Red Hat OpenShift Container Platform. - -### Amazon Linux 2023 support - -Percona Server for MongoDB is now available and fully supported on Amazon Linux 2023 (AL23), simplifying its AWS deployment. You can safely run Percona Server for MongoDB on AL23 to build a secure, stable, high-performance environment for developing and running cloud applications, with seamless integration with various AWS services and development tools. You can download a tarball and a RPM from our [Percona Software Downloads](https://www.percona.com/downloads) page. Navigate to the Percona Server for the MongoDB section, select the version, and choose `AMAZON LINUX 2023` Platform for RPMs or `LINUX - GENERIC` for tarballs. - -## Changelog - -### Fixed Bugs - -* [PSMDB-1243](https://perconadev.atlassian.net/browse/PSMDB-1243) - Fixed the issue with starting Percona Server for MongoDB Docker container with data-at-rest encryption configured via the configuration file - -* [PSMDB-1573](https://perconadev.atlassian.net/browse/PSMDB-1573) - Added escaping of special characters when building LDAP queries - -* [PSMDB-1567](https://perconadev.atlassian.net/browse/PSMDB-1567) - Fixed the issue with the crashing server during LDAP authentication when the LDAP server is down. - diff --git a/docs/release_notes/8.0.8-3.md b/docs/release_notes/8.0.8-3.md deleted file mode 100644 index b1de1be4e..000000000 --- a/docs/release_notes/8.0.8-3.md +++ /dev/null @@ -1,94 +0,0 @@ -title: Percona Server for MongoDB 8.0.8-3 ({{date.8_0_8}}) -summary: Learn about improvements, new features, and bug and security vulnerability fixes in this release -authors: - - Anastasia Alexandrova -version: 8.0.8-3 ---- - -# Percona Server for MongoDB {{ page.meta.version }} ({{date.8_0_8}}) - -[Install](../install/index.md){.md-button} -[Upgrade from MongoDB Community](../install/upgrade-from-mongodb.md){.md-button} - -Percona Server for MongoDB {{ page.meta.version }} 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 {{ page.meta.version }} includes the improvements and bug fixes of [MongoDB 8.0.5 Community Edition](https://www.mongodb.com/docs/manual/release-notes/8.0/#8.0.5---feb-20--2025), [MongoDB 8.0.6 Community Edition](https://www.mongodb.com/docs/manual/release-notes/8.0/#8.0.6---mar-19--2025), [MongoDB 8.0.7 Community Edition](https://www.mongodb.com/docs/manual/release-notes/8.0/#8.0.7---apr-14--2025) and [MongoDB 8.0.8 Community Edition](https://www.mongodb.com/docs/manual/release-notes/8.0/#8.0.8---apr-14--2025). - -It supports protocols and drivers of MongoDB Community 8.0.5 through 8.0.8. - - -## Release Highlights - -This release provides the following features and improvements: - -### Improved compatibility for data-at-rest encryption using KMIP between Percona Server for MongoDB with 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. - -*Update from {{date.pro_eol}}: We no longer release Percona Server for MongoDB Pro Builds. All features included in Pro Builds are accessible for everyone in our public regular builds. If you need a Pro Build for that specific version, please contact your Percona representative for guidance. We're here to help ensure a smooth transition and continued success with Percona open-source solutions.* - - -### 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 8.0.8-3 is compatible only with Amazon Linux 2023.7.x and won't work on Amazon Linux 2023.6.x and older. - -To upgrade to 8.0.8-3, make sure that you run Amazon Linux 2023.7.x. Use the [update instructions :octicons-link-external-16:](https://docs.aws.amazon.com/linux/al2023/ug/updating.html) - - -### Upstream Improvements - -The bug fixes, provided by MongoDB Community Edition and included in Percona Server for MongoDB, are the following: - -* [SERVER-51366](https://jira.mongodb.org/browse/SERVER-51366) - Changed permissions to the binaries directory when MongoDB is installed using the Windows MSI (Microsoft Installer) package to match between ProgramFiles and custom location -* [SERVER-93497](https://jira.mongodb.org/browse/SERVER-93497) - Fixed the issue with using the outdated data by moving user cache invalidation to an `onCommit` handler, created inside of the OpObserver callback, when user's roles get modified -* [SERVER-97044](https://jira.mongodb.org/browse/SERVER-97044) - Fixed an issue where change streams might incorrectly output a "drop" event during resharding or unsharding of a collection that is or was using zone sharding -* [SERVER-97860](https://jira.mongodb.org/browse/SERVER-97860) - Fixed the issue with express path returning incorrect results when scanning a unique, multi-field index. The issue occurred when running a query where a predicate is not the `_id` field or a sharded collection has a compound unique index that includes the field used in the query and it doesn't have a unique index. The recommendation is to update to version 8.0.6. Follow closely the upstream recommendations for workaround if you don't wish to upgrade yet -* [SERVER-99290](https://jira.mongodb.org/browse/SERVER-99290) - Reduced the strictness of the feature compatibility version check to allow a customer with inconsistent buckets collection to upgrade to FCV 8.0 -* [SERVER-99345](https://jira.mongodb.org/browse/SERVER-99345) - Prevented sharding/moving a time-series buckets collection without the 'timeseries' options on FCV 8.0 and above -* [SERVER-97911](https://jira.mongodb.org/browse/SERVER-97911) - Fixed the performance regression when MongoDB travers an entire collection before reporting no results instead of doing it immediately when an ` -_id` is given as a hint for a query -* [SERVER-100901](https://jira.mongodb.org/browse/SERVER-100901) - Reduced 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 -* [SERVER-103328](https://jira.mongodb.org/browse/SERVER-103328) - Fixed BSONColumnBuilder handling for rescaling after skip for double type - -Find the full list of changes in the [MongoDB 8.0.5 Community Edition](https://www.mongodb.com/docs/manual/release-notes/8.0/#8.0.5---feb-20--2025), [MongoDB 8.0.6 Community Edition](https://www.mongodb.com/docs/manual/release-notes/8.0/#8.0.6---mar-19--2025), [MongoDB 8.0.7 Community Edition](https://www.mongodb.com/docs/manual/release-notes/8.0/#8.0.7---apr-14--2025) and [MongoDB 8.0.8 Community Edition](https://www.mongodb.com/docs/manual/release-notes/8.0/#8.0.8---apr-14--2025) release notes. - -## Changelog - -### New Features - -* [PSMDB-1282](https://perconadev.atlassian.net/browse/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](https://perconadev.atlassian.net/browse/PSMDB-1620) - Do not create an empty audit log file if the log destination is not `file` - -* [PSMDB-1621](https://perconadev.atlassian.net/browse/PSMDB-1621) - Check if an audit log file can be opened for writing at default path - -### Fixed Bugs - -* [PSMDB-118](https://perconadev.atlassian.net/browse/PSMDB-118) - Fixed the audit log file extension to be created based on the specified audit log format. - -* [PSMDB-121](https://perconadev.atlassian.net/browse/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](https://perconadev.atlassian.net/browse/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](https://perconadev.atlassian.net/browse/PSMDB-1392) - Ensured that `$backupCursor` returns `oplogEnd` without holes (Thank you MingTotti Guoming He for reporting this issue) - -* [PSMDB-1614](https://perconadev.atlassian.net/browse/PSMDB-1614) - Replaced a hard-coded port number with a placeholder in percona-server-enable-authentication.sh - -* [PSMDB-1617](https://perconadev.atlassian.net/browse/PSMDB-1617) - Improved error messages when there are insufficient permissions to access client/CA certificates for KMIP authentication \ No newline at end of file diff --git a/docs/release_notes/8.0.4-1.md b/docs/release_notes/8.3.4-1.md similarity index 99% rename from docs/release_notes/8.0.4-1.md rename to docs/release_notes/8.3.4-1.md index 5ec260bd5..9f6df963f 100644 --- a/docs/release_notes/8.0.4-1.md +++ b/docs/release_notes/8.3.4-1.md @@ -1,8 +1,8 @@ -title: Percona Server for MongoDB release notes version 8.0.4-1 +title: Percona Server for MongoDB release notes version 8.3.4-1 summary: Get to know all improvements, new features, and bug and security vulnerability fixes in the release authors: - - Anastasia Alexandrova -version: 8.0.4-1 + - Rasika Chivate +version: 8.3.4-1 --- # Percona Server for MongoDB {{ page.meta.version }} ({{date.8_0_4}}) From 37a643685e4fc76bfbc37eb56b954f3723987dfc Mon Sep 17 00:00:00 2001 From: rasika-chivate <95711051+rasika-chivate@users.noreply.github.com> Date: Wed, 22 Jul 2026 19:09:13 +0530 Subject: [PATCH 02/41] Update 8.3.4-1.md --- docs/release_notes/8.3.4-1.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/release_notes/8.3.4-1.md b/docs/release_notes/8.3.4-1.md index 9f6df963f..a92aeddea 100644 --- a/docs/release_notes/8.3.4-1.md +++ b/docs/release_notes/8.3.4-1.md @@ -5,14 +5,14 @@ authors: version: 8.3.4-1 --- -# Percona Server for MongoDB {{ page.meta.version }} ({{date.8_0_4}}) +# Percona Server for MongoDB {{ page.meta.version }} ({{date.8_3_4}}) [Installation](../install/index.md){.md-button} [Upgrade](../install/upgrade-from-70.md){.md-button} -We are pleased to announce the new major version of Percona Server for MongoDB 8.0.4-1 – the drop in replacement for MongoDB Community Edition. Percona Server for MongoDB supports MongoDB Community protocols and drivers and enhances it with the [enterprise-grade features for free](../comparison.md), enabling you to effectively meet the requirements of your organization in terms of high-availability, reliability and data security. +We are pleased to announce the new major version of Percona Server for MongoDB 8.3.4-1 – the drop in replacement for MongoDB Community Edition. Percona Server for MongoDB supports MongoDB Community protocols and drivers and enhances it with the [enterprise-grade features for free](../comparison.md), enabling you to effectively meet the requirements of your organization in terms of high-availability, reliability and data security. -This release of Percona Server for MongoDB includes the improvements and bug fixes of [MongoDB 8.0.0 Community Edition](https://www.mongodb.com/docs/manual/release-notes/8.0/#8.0.0---oct-2--2024) through [MongoDB 8.0.4 Community Edition](https://www.mongodb.com/docs/manual/release-notes/8.0/#8.0.4---dec-9--2024). +This release of Percona Server for MongoDB includes the improvements and bug fixes of [MongoDB 8.3.4 Community Edition](https://www.mongodb.com/docs/manual/release-notes/8.3/#8.3.4---june-11--2026). ## Upgrade considerations From d82cf79bc4cfa204145bb1aa61618fb836494c40 Mon Sep 17 00:00:00 2001 From: rasika-chivate <95711051+rasika-chivate@users.noreply.github.com> Date: Wed, 22 Jul 2026 19:19:33 +0530 Subject: [PATCH 03/41] Update 8.3.4-1.md --- docs/release_notes/8.3.4-1.md | 73 ++--------------------------------- 1 file changed, 3 insertions(+), 70 deletions(-) diff --git a/docs/release_notes/8.3.4-1.md b/docs/release_notes/8.3.4-1.md index a92aeddea..6176fcb82 100644 --- a/docs/release_notes/8.3.4-1.md +++ b/docs/release_notes/8.3.4-1.md @@ -14,22 +14,13 @@ We are pleased to announce the new major version of Percona Server for MongoDB 8 This release of Percona Server for MongoDB includes the improvements and bug fixes of [MongoDB 8.3.4 Community Edition](https://www.mongodb.com/docs/manual/release-notes/8.3/#8.3.4---june-11--2026). -## Upgrade considerations - -Starting with version 8.0, Percona Server for MongoDB uses the upgraded TCMalloc to handle memory requests more efficiently. The use of TCMalloc requires you to enable Transparent Huge Pages (THP) and per-CPU caches before you start Percona Server for MongoDB. In MongoDB 8.0 and later, ensure that THP is enabled before mongod starts by creating a service file for your platform's initialization system. If you are using MongoDB 7.0 or earlier - disable THP. - -Read more about TCMalloc in [MongoDB documentation :octicons-link-external-16:](https://www.mongodb.com/docs/manual/administration/tcmalloc-performance/). ## Release Highlights In addition to the [upstream improvements](#upstream-improvements), Percona Server for MongoDB features the following improvements: -### Prevent master encryption key loss on the Vault server - -Before Percona Server for MongoDB puts a new master encryption key to the Vault server as the versioned secret, it now checks if the secret's version reached the defined maximum (10 by default). This prevents the loss of the old secret and the master encryption key it stores on the Vault server. - -Make sure Percona Server for MongoDB has read permissions for the secret's metadata and the secrets engine configuration. To learn more, refer to the [documentation](../vault.md#master-key-loss-prevention). +### ### Join Percona Squad @@ -37,67 +28,12 @@ Participate in monthly SWAG raffles, get an early access to new product features ### Upstream Improvements -MongoDB 8.0 introduces a lot of major changes. We recommend testing it on staging environments before using it in production. The features and improvements in MongoDB 8.0 are focused on the following main areas: - -#### Performance improvements - -* Benefit from faster performance when working with time series collections. A new algorithm enhances time series speed by processing queries in "blocks" of data rather than individual values. -* Insert operations for multi-document transactions no longer produce single oplog entries. Instead, they are now batched as a single entry. This change increases multi-document insert performance and improves replication efficiency, reducing lag. -* Oplog buffers for replication are now introduced. A new writer thread reads new entries from the primary and writes them to the local oplog on each secondary. An independent applier thread asynchronously applies changes to the local database, increasing replication throughput. -* The upgraded TCMalloc version is now the default in MongoDB. Together with THP and per-CPU cache, it reduces memory fragmentation by 18% which is especially useful during peak loads. - -#### Workload management - -Analyze query performance and manage the workload in your system using [query shapes](https://www.mongodb.com/docs/manual/core/query-shapes/#std-label-query-shapes). A query shape is a set of specifications to group similar queries together. For a query shape, you add query settings instead of index filters. Query settings are persistent meaning that they remain after the cluster restart thus saving you from rerunning them in your application. A query shape has the `queryShapeHash` parameter using which you can check if the operation causes excessive workload and deny it using operation rejection filters. - -#### Developer experience +MongoDB 8.3 introduces a lot of major changes. We recommend testing it on staging environments before using it in production. The features and improvements in MongoDB 8.3 are focused on the following main areas: -* Insert, update or delete multiple collections in one request with the new [`bulkWrite`](https://www.mongodb.com/docs/manual/reference/command/bulkWrite/#mongodb-dbcommand-dbcmd.bulkWrite) command. Previously you could only run these operations on a single collection. -* Several enhancements are made to the index build process such as a better error handling and tolerance to disk space issues. This avoids common secondary crashes due to errors. - - -#### Sharding improvements - -* To better optimize resources or distribute the data more evenly across the shards, you can now [move a single unsharded collection to any shard](https://www.mongodb.com/docs/manual/core/moveable-collections/#std-label-moveable-collections) with the new `moveCollection` command. This operation is going online and the collection data is fully available during the migration. This new way to move data is flexible and the read and write behavior when you query data is transparent. -* Ensuring even data distribution across shards in your cluster is crucial. Starting with MongoDB 5.0, you can reshard a collection using a different shard key, although this operation is time-consuming. In MongoDB 8.0, you can reshard a collection using the same shard key, significantly boosting performance. This is especially beneficial for large collections, reducing resharding time from days to several hours. You can dynamically reallocate your resources based on the workload. The process is online, so your operations run uninterrupted. The ability to add or remove shards without changing the shard key makes the whole resharding process straightforward. -* You can now [unshard a collection](https://www.mongodb.com/docs/manual/tutorial/unshard-collection/#std-label-unshard-collection-task) if it should reside on a single shard or the collection requires resource isolation. You can either specify the desired shard or the collection will be moved onto the shard with the least load. -* You can now save costs on additional computing resources when deploying a sharded cluster. The config server replica set can now store both the configuration and the database data. Such a deployment is recommended for small clusters and is especially useful for evaluating the cluster without having to pay extra costs. -* You can now make self-managed backups in sharded clusters using `mongodump`. Run the [`fsync`](https://www.mongodb.com/docs/manual/reference/command/fsync/#mongodb-dbcommand-dbcmd.fsync) command with the `lock` field set to `true` from `mongos` to lock each shard and prevent further writes. Then, run `fsynckUnlock` to unlock shards. Note that this process blocks all database writes while the fsync is in place. - -#### Logging improvements - -You can now configure database profiler to log slow operations based on the time MongoDB actually spent processing that operation. This gives you more accuracy when you analyze performance. - -#### Security improvements - -* You can now run range queries on encrypted fields, specifically for numeric data types and dates. This expands the range of use cases for Manual Queryable Encryption, including accounting operations, healthcare, financial services, and other strictly regulated data operations where data safety is crucial. Other improvements include the following: -* [SERVER-73641](https://jira.mongodb.org/browse/SERVER-73641) - Fix the issue with timeseries filtering missing extended-range events when sharded -* [SERVER-82037](https://jira.mongodb.org/browse/SERVER-82037) - Fixed the issue with extreme memory usage by sorter by limiting the number of file iterators a sorter can create -* [SERVER-94559](https://jira.mongodb.org/browse/SERVER-94559) - Fixed the issue with tracking the archived bucket based on the minTime in the bucket registry for time series measurements by leaving the bucket's minTime unchanged when performing user deletes/updates on it -* [SERVER-95067](https://jira.mongodb.org/browse/SERVER-95067) - Handle multiple batches per bucket in time-series insert -* [SERVER-95724](https://jira.mongodb.org/browse/SERVER-95724) - Make resharding unroll multiple applyOps when it clones the retryable write session info to a recipient -* [SERVER-93205](https://jira.mongodb.org/browse/SERVER-93205) - Enabled the `indexStats` section of the `serverStatus` command output to track indexes in the `prepareUnique` state. -* [SERVER-92762](https://jira.mongodb.org/browse/SERVER-92762) - Improved the resilience and performance of sharding in the cluster by setting the default value of `numInitialChunks` in `reshardCollection` to 90. -* [SERVER-91777](https://jira.mongodb.org/browse/SERVER-91777) - Disabled oplog sampling during restore procedure to optimize the restore time -* [SERVER-90965](https://jira.mongodb.org/browse/SERVER-90965) - Extended query settings to include optional comment field. This may be helpful to persist details about a change for audit or easier troubleshooting. Read more in https://www.mongodb.com/docs/manual/reference/command/setQuerySettings/ -* [WT-13377](https://jira.mongodb.org/browse/WT-13377) - Reconfiguring a session with `cache_max_wait_ms` now accepts a value of zero -* [SERVER-94970](https://jira.mongodb.org/browse/SERVER-94970) - Fixed the issue with sharded `$searchMeta` queries in a `$lookup` and `$unionWith` failing by hitting an `unreachable_tassert` -* [SERVER-95240](https://jira.mongodb.org/browse/SERVER-95240) - Removed PeerID from SSL handshakes -* [SERVER-95067](https://jira.mongodb.org/browse/SERVER-95067) - Fixed the issue with time-series inserts generating multiple batches referencing the same bucket. -* [SERVER-84769](https://jira.mongodb.org/browse/SERVER-84769) - Changed the resharding remainingOpTime algorithm by adding initial delay to resharding commit monitor query -* [SERVER-67816](https://jira.mongodb.org/browse/SERVER-67816) - Fixed time rounding for timeseries control block of dates prior to 1970 -* [SERVER-96419](https://jira.mongodb.org/browse/SERVER-96419) - Fixed the issue with improper neutralization of null bytes that may have led to buffer over-reads in MongoDB Server -* [SERVER-95279](https://jira.mongodb.org/browse/SERVER-95279) - Use a new C++ type for BSON field names to ensure validity -* [SERVER-76883](https://jira.mongodb.org/browse/SERVER-76883) - Suppressed the "role does not exist" warning log for LDAP group role resolution -* [SERVER-82221](https://jira.mongodb.org/browse/SERVER-82221) - Included commit-pending metadata entries to the listCollections and listIndexes output -* [SERVER-94635](https://jira.mongodb.org/browse/SERVER-94635) - Improved handling of logical session refresh by making the session refresh parameters configurable -* [SERVER-95244](https://jira.mongodb.org/browse/SERVER-95244) - Fixed the `tassert()` failure for upsert operations run when a client connects directly to shard -* [WT-13409](https://jira.mongodb.org/browse/WT-13409) - Fixed the data corruption issue by properly handling a return value from a function call in transaction checkpoint in WiredTiger - -Find the full list of changes in the [MongoDB 8.0.4 Community Edition release notes](https://www.mongodb.com/docs/manual/release-notes/8.0/#8.0.4---dec-9--2024). + ## Changelog @@ -105,9 +41,6 @@ Find the full list of changes in the [MongoDB 8.0.4 Community Edition release no * [PSMDB-1441](https://perconadev.atlassian.net/browse/PSMDB-1441) - Fixed the issue with master encryption keys getting lost when the number of created secrets exceeds the threshold by preventing a new secret creation and alerting users about it. -### Fixed Bugs - -* [PSMDB-1527](https://perconadev.atlassian.net/browse/PSMDB-1527) - Improve the activateKeys option handling by changing its type to boolean. From a12dd4cd5943aa82a3fe8396f43cfe6f53736ef3 Mon Sep 17 00:00:00 2001 From: rasika-chivate <95711051+rasika-chivate@users.noreply.github.com> Date: Wed, 22 Jul 2026 19:49:42 +0530 Subject: [PATCH 04/41] update config files --- docs/_templates/pdf_cover_page.tpl | 4 ++-- variables.yml | 16 +++------------- 2 files changed, 5 insertions(+), 15 deletions(-) diff --git a/docs/_templates/pdf_cover_page.tpl b/docs/_templates/pdf_cover_page.tpl index e4e02ed04..0d6cad3c5 100644 --- a/docs/_templates/pdf_cover_page.tpl +++ b/docs/_templates/pdf_cover_page.tpl @@ -3,10 +3,10 @@