Docs Menu
Docs Home
MongoDB Cluster-to-Cluster Sync

Release Notes for mongosync 1.4

On this page

  • Patch Releases
  • 1.4.1 - June 23, 2023
  • 1.4.0 Release
  • Set Cluster Workload Level
  • Faster Processing
  • Improved Memory Handling
  • Telemetry
  • Bug Fixes
  • Additional Considerations
  • Minimum Supported Version

Issues fixed:

  • Fixes a build misconfiguration so that telemetry information is sent correctly.

June 21, 2023

Starting in 1.4.0, you can set the workload level that Cluster-to-Cluster Sync uses to sync data between the source and destination clusters. For more information, see the --loadLevel option.

Version 1.4.0 improves change event application speeds for improved performance.

In version 1.4.0, mongosync uses less memory to buffer change events. Improved memory handling alleviates some out-of-memory (OOM) issues.

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.

  • Fixes an issue so documents with _id values that evaluate to the same string replicate correctly.

  • Fixes a collection naming issue. Prior to version 1.4.0, mongosync crashes when a new collection reuses a dropped collection's name with letter case changes.

    For example, previous versions of mongosync crash if a new SampleName collection replaces the dropped samplename collection.

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.

In 1.4.0, the minimum supported version of MongoDB is 6.0.5.

← Release Notes for mongosync 1.5