Percona Link for MongoDB 0.6.0 (2025-09-04) (Technical preview)¶
We are excited to announce the first public release of Percona Link for MongoDB (PLM). It is in technical preview stage. We encourage you to test it and give us your feedback. This will help us improve the product in future.
Percona Link for MongoDB (PLM) is a tool for replicating data from a source MongoDB cluster to a target MongoDB cluster. It enables you to migrate from MongoDB Atlas or MongoDB Enterprise Edition to Percona Server for MongoDB with zero downtime. Check Supported MongoDB deployments.
Percona Link for MongoDB (PLM) supports cloning data, replicating changes, and managing collections and indexes.
Release highlights¶
This release provides the following improvements:
Replication of both unique and non-unique indexes defined on the same fields¶
Now PLM not only properly reports failed or skipped index creations during the finalization stage, it also tries to automatically re-create these indexes. It re-creates a non-unique index as a unique one and then creates the original non-unique index. This way, PLM can now replicate both unique and non-unique indexes on the same fields, which was not possible before. This makes the replication process more reliable and comprehensive.
Namespace management for replication via CLI¶
You can now leverage both CLI and the API to define what namespaces to include or exclude for replication. This enables you to optimize resource utilization and manage the load on your source and target clusters by replicating only the data you care about.
Changelog¶
Improvements¶
-
PLM-131 - Add proper replication of both unique and non-unique indexes on the same fields, provide a more user-friendly report for index creation failures and try to re-create failed indexes during finalization stage.
-
PLM-127 - Added the ability to use include and exclude filters for namespaces via the command-line interface, making it easier to manage selective replication.
-
PLM-172 - Added retryable write operations across all PLM components to improve reliability and prevent failures due to transient errors.
-
PLM-173 - Improved the catalog component’s lock usage to prevent long-held write locks from blocking readers.
Fixed bugs¶
- PLM-126 - Fixed an issue where PLM would not sync data for an entire collection if a record had a Not a Number ‘NaN’ ID, leading to a synchronization failure.
- PLM-146 - Fixed an issue where renaming a collection multiple times in a row could cause the operation to fail.
- PLM-147 - Fixed an issue where PLM would fail during the data clone stage if the
_id
index was dropped. - PLM-155 - Fixed an issue that prevented PLM from proceeding with replication when the primary on the destination changed. Now it properly handles the primary change and retries the replication.
- PLM-178 - Fixed an issue where selective replication using
exclude
andinclude
filters did not work correctly, and it would instead exclude all collections in the specified databases. - PLM-184 - Fixed the issue with Percona Server for MongoDB 6.0 failing during the replication if retries of
createCollection
afterInterruptedDueToReplStateChange
returnNamespaceExists
error. It is fixed by ignoring theNamespaceExists
error. - PLM-187 - Fixed the issue with PLM crashing during data clone by setting proper capacity for
builtIndexes
slices
Created: September 8, 2025