Skip to content

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

Percona Server for MongoDB 6.0.24-19 (2025-06-12)

Installation Upgrade from MongoDB Community

Percona Server for MongoDB 6.0.24-19 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 6.0.22 Community Edition through MongoDB 6.0.24 Community Edition and supports the upstream protocols and drivers of all these versions.

Release Highlights

Packaging changes

Regular builds of Percona Server for MongoDB 6.0.24-19 are no longer supported on Ubuntu 20.04 (Focal Fossa) as this operating system has reached end of life. However, if for some reason you’re not yet able to upgrade to a newer Ubuntu OS and you’d like to still upgrade your Percona Server for MongoDB, contact us - 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-93120 - Fixed the issue with blocking Full Time Diagnostic Data Capture (FTDC) collection when checking the state of the bacupCursor by using atomic mode instead of a lock
  • SERVER-82037 - Fixed the issue with exceeding the amount of memory allocated for index creation by limiting the number of file iterators a sorter can create
  • SERVER-88400 - Fixed the issue with the shardedDataDistribution aggregation stage returning null value for timeseries when executed against bucket collections by computing metrics based on timeseries.bucketCount and timeseries.avgBucketSize
  • SERVER-92806 - Tracked nested paths through MatchExpression trees while encoding indexability for plan cache entries
  • SERVER-95976 - Introduced the “matchCollectionUUIDForUpdateLookup” parameter to enforce updateLookup to only return a document from the correct collection in the changestream stage
  • WT-13283 - Fixed the bug where WiredTiger “cache aggressive mode” for better cache usage showed the “garbage values” by applying the compare-and-swap operation to the code to avoid the value dropping to -1(which is int_max as evict_aggressive_score is an unsigned int)

Find the full list of changes in the release notes of MongoDB 6.0.22 Community Edition through MongoDB 6.0.24 Community Edition.