Skip to content

Percona Server for MongoDB 4.4.12-12 (2022-02-07)

Release date February 7, 2022
Installation Installing Percona Server for MongoDB

Percona Server for MongoDB 4.4.12-12 is an enhanced, source-available and highly-scalable database that is a fully-compatible, drop-in replacement for MongoDB Community Edition. It is based on MongoDB 4.4.11 and 4.4.12 and supports MongoDB 4.4.11 - 4.4.12 protocols and drivers.

Warning

Inconsistent data is observed after the upgrade from MongoDB 4.4.3 and 4.4.4 to versions 4.4.8+ and 5.0.2+. This issue is fixed upstream in versions 4.4.11 and 5.0.6. Percona Server for MongoDB also includes the fix in versions 4.4.12-12 and 5.0.6-5

See the upgrade recommendations below:

  • Clusters on versions 4.4.0 and 4.4.1 are safe to upgrade to 4.4.8+ or 5.0.2+ but should upgrade to recommended versions 4.4.11+ or 5.0.5+

  • Clusters on versions 4.4.2, 4.4.3, or 4.4.4 should downgrade to 4.4.1 and then upgrade to versions 4.4.11+ or 5.0.5+.

  • Clusters running versions 4.4.5 - 4.4.7 can and should upgrade to versions 4.4.11+ or 5.0.5+.

Note that clusters running versions 4.4.2 - 4.4.8 are affected by the bug WT-7995. See WT-7995 for specific explanation and instructions on running the validate command to check for data inconsistencies. These data inconsistencies can lead to data loss if not identified and repaired at this point between versions 4.4.8 and 4.4.9.

If the validate command output reports any failures, resync the impacted node from an unaffected node. The validate command must be run against all collections in the database. This process can be resource intensive and can negatively impact performance.

Release Highlights

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

  • WT-8395 - Fixed an issue with inconsistent data observed during the direct upgrade from from 4.4.3 and 4.4.4 to 4.4.8+ and 5.0.2+. Data inconsistency was caused by the incorrect checkpoint metadata to sometimes be recorded by MongoDB versions 4.4.3 and 4.4.4. WiredTiger used this metadata during node startup that could lead to data corruption and could cause the DuplicateKey error. The fix requires the upgrade to versions 4.4.11+ or 5.0.5+.

  • SERVER-61930 - Defined a timeout for a health check process and throw an error when the process fails to complete within a timeout. This prevents health check to hang.

  • SERVER-61637 - Changed the rangeDeleterBatchSize value to unlimited to avoid the balancer starvation during batched deletes.

  • SERVER-59362 - Added the ability to transition through the valid states of the fault manager, and the interface to observer and log its state transitions.

  • SERVER-62147 - Fixed broken OP_QUERY exhaust cursor implementation

  • SERVER-62065 - Added the repairShardedCollectionChunksHistory command to restore history fields for some chunks. This aims to fix broken snapshot reads and distributed transactions.

Find the full list of changes in the MongoDB 4.4.11 Community Edition and MongoDB 4.4.12 Community Edition release notes

Bugs Fixed

  • PSMDB-756: Fixed an issue with unmet dependencies for installing MongoDB on Debian (Thanks to Stefan Schlesi for reporting this issue)

  • PSMDB-950: Fixed LDAP authentication using mongo CLI for Percona Server for MongoDB installed from a tarball.

Get expert help

If you need assistance, visit the community forum for comprehensive and free database knowledge, or contact our Percona Database Experts for professional support and services.