Percona Distribution for MongoDB 5.0.10 (2022-08-09)¶
August 9, 2022
We don’t recommend this version for the production use due to the critical issue with sharding metadata inconsistency: SERVER-68511. The metadata inconsistency is observed when running the
movePrimary command on the database that has the Feature Compatibility Version (FCV) set to 4.4 or earlier. Affects MongoDB versions 5.0.0 through 5.0.10 and MongoDB 6.0.0. Upgrade to the fixed version of MongoDB 5.0.11 / Percona Server for MongoDB 5.0.11-10 or Percona Distribution for MongoDB 5.0.11 as soon as possible.
Please follow closely the upstream recommendations outlined in SERVER-68511 to work around this issue and for the remediation steps, if your cluster is affected.
Percona Distribution for MongoDB is a freely available MongoDB database alternative, giving you a single solution that combines enterprise components from the open source community, designed and tested to work together. The aim of Percona Distribution for MongoDB is to enable you to run and operate your MongoDB efficiently with the data being consistently backed up.
Percona Distribution for MongoDB includes the following components:
Percona Server for MongoDB is a fully compatible source-available, drop-in replacement for MongoDB.
Percona Backup for MongoDB is a distributed, low-impact solution for achieving consistent backups of MongoDB sharded clusters and replica sets.
This release of Percona Distribution for MongoDB includes bug fixes and improvements provided by MongoDB and included in Percona Server for MongoDB. It specifically includes multiple fixes related to sharding and the resharding operation.
Fixed the issue with bad projection created during dependency analysis due to string order assumption. It resulted in the
PathCollisionerror. The issue is fixed by improving dependency analysis for projections by folding dependencies into ancestor dependencies where possible.
Fixed the deadlock situation in cross shard transactions that could occur when the FCV (Feature Compatibility Version) was set after the “prepared” state of the transactions. That ended up with both the the setFCV thread and the
This is a v6.0 backport fix to v5.0 that disables opportunistic read targeting (except for specified hedged reads) in order to prevent possible performance problems associated with uneven read distribution across the secondaries.
Backported the check for user errors in case deadline on the migration destination manager is hit while waiting for a range to be cleared up. This prevents the balancer from getting blocked.
Fixed the situation where the shards may skip certain steps in the resharding process but respond to the resharding coordinator as if they had. This can cause the resharding coordinator to continue to wait for updated states in the
config.reshardingOperationsdocument on the primary config server and stall indefinitely.
Fixed the potential for the range deleter to wait unnecessarily during concurrent migrations between batches.
Fixed the issue where 2 very different measurements (one in the past and one in future) could be incorrectly included in the same buckettime-series bucket.
Resolved potential problem when adding or removing shards and incorrectly gossiping a new topology time without it being majorly committed.
Percona Backup for MongoDB 1.8.1 improvements include the following:
Fixed the restore failure on a different cluster. Now the UUID of users and system collections are not preserved when replaying the oplog.
The Point-in-Time recovery chunks display is now consistent in both
Debian 9 (“Stretch”) is no longer supported.