mongosync. View the
current documentation
for up-to-date guidance on mongosync and instructions on how to upgrade
to the latest version.Warning
Past Release Limitations
The Critical Advisories below affect some prior mongosync
versions. Upgrade to the latest available patch release.
Issue | Affected Versions |
|---|---|
| 1.1.0 - 1.7.1 |
Patch Releases
1.4.1 - June 23, 2023
Issues fixed:
Fixes a build misconfiguration so that telemetry information is sent correctly.
1.4.0 Release
June 21, 2023
Set Cluster Workload Level
Starting in 1.4.0, you can set the workload level that
Mongosync uses to sync data between the source and
destination clusters. For more information, see the
--loadLevel option.
Faster Processing
Version 1.4.0 improves change event application speeds for improved
performance.
Improved Memory Handling
In version 1.4.0, mongosync uses less memory to buffer change
events. Improved memory handling alleviates some out-of-memory (OOM)
issues.
Telemetry
Starting in 1.4.0, mongosync collects anonymous, aggregated usage
data to improve MongoDB products. You can disable collection of this
telemetry data when you start mongosync.
Bug Fixes
Fixes an issue so documents with
_idvalues that evaluate to the same string replicate correctly.Fixes a collection naming issue. Prior to version 1.4.0,
mongosynccrashes when a new collection reuses a dropped collection's name with letter case changes.For example, previous versions of
mongosynccrash if a newSampleNamecollection replaces the droppedsamplenamecollection.
Additional Considerations
The MongoDB server's validate command may report data
corruption on destination clusters that run MongoDB version 6.0 through
6.0.6. The data on the destination server is not corrupt. A bug in the
WiredTiger database engine,
WT-11051, causes the false report.
Minimum Supported Version
In 1.4.0, the minimum supported version of MongoDB is 6.0.5.