Release Notes for mongosync 1.22

mongosync now performs a check of the available disk space on the destination cluster before it starts a migration. If the estimated space that the migration requires exceeds the available space, /start returns an InsufficientDestinationDiskSpace error and the migration does not start. To skip the check, such as in situations where the destination's file system storage does not accurately reflect available storage, set skipDiskSpaceCheck to true when you call /start. See Destination Disk Space and Request Body Parameters for more details.

Adds the ceaStage field to the /progress API response. The ceaStage field reports whether Change Event Application (CEA) is still draining the backlog of change events that accumulated during collection copy or is now applying change events that occurred after collection copy finished. See progress for more details.

The embedded verifier now starts at the Change Event Application (CEA) phase by default. Migrations that run with verification complete faster and more reliably. During collection copy, the /progress endpoint now reports the verifier phase as "not started". See Verify with Embedded Verifier for more details.

Fixes an issue where lagTimeSeconds increased indefinitely when a migration included capped collections.

mongosync is no longer released for Amazon Linux 2, which reached end-of-life on June 30, 2026. To migrate from a host that runs Amazon Linux 2, use mongosync 1.21.

mongosync no longer provides x86-64 builds for macOS. mongosync provides only ARM64 builds for macOS.

mongosync is now built with Go 1.26.7.