Release Notes for mongosync 1.14

This page describes changes and new features introduced in MongoDB Mongosync 1.14.

1.14.0 Release

June 5, 2025

Adds the estimatedSecondsToCEACatchup field to the progress endpoint response.
mongosync errors on indexes that are inconsistent or missing on some data-bearing shards, instead of ignoring them.
Adds the "excludeHashed" option to the buildIndexes parameter in the start endpoint.

Live upgrades to 1.14 are not supported.

Fixes a bug where mongosync exited during collection copy upon seeing a transient error. Now, mongosync will retry on retryable errors.
Fixes a bug where the embedded verifier could have caused long downtime during commit if the source cluster has a lot of unique or hidden indexes.

Fixes a case where mongosync exited unexpectedly without printing a fatal log error. Now, if mongosync exits unexpectedly, it prints a log error.
Fixes a bug introduced in mongosync version 1.10 where the progress endpoint overcounted the verifier's estimatedDocumentCount.
If the verifier finds checksum mismatches, it might re-fetch some documents from the source or destination cluster to check if the mismatch is due to differences in field order. This might lead to cutover taking slightly longer.

For information on minimum supported versions, see MongoDB Server Version Compatibility.

For best performance, upgrade your source and destination clusters to the most recent MongoDB Server patch release prior to migration. For more information, see Upgrade to the Latest Self-Managed Patch Release of MongoDB.

Back

1.15

1.13