Release Notes for mongosync 1.5

Warning

Past Release Limitations

The Critical Advisories below affect some prior mongosync versions. Upgrade to the latest available patch release.

Issue	Affected Versions
`mongosync` could miss change events when reading documents from a lagging secondary node.	1.5.0 - 1.7.1
`mongosync` could miss copying documents during long running reads in the initial copying phase if the source cluster is sharded and the source balancer is enabled.	1.1.0 - 1.7.1

1.5.0 Release

July 25, 2023

Oplog Rollover Resilience

Starting in 1.5.0, mongosync begins to apply changes while the initial sync is still in progress. By starting to apply changes earlier, mongosync maintains a more recent position in the oplog. This adds resilience to long-running operations, mitigates the risk of oplog rollover, and significantly lowers the risk of restarting the sync.

Logging Level

Starting in 1.5.0, the default logging level is DEBUG. To change the logging level, see the verbosity setting.

Bug Fixes

Fixes an issue where very large collections could timeout during mongosync initialization.
Fixes an issue where mongosync could incorrectly report indexes as mismatched.
Fixes an issue where the /start endpoint would not return an error when passed a sharding object without the shardingEntries key.
Changes telemetry to send less metadata to Segment.

Minimum Supported Version

In 1.5, the minimum supported version of MongoDB is 6.0.8.

Back

1.6

1.4