Docs Menu
Docs Home
MongoDB Atlas
/ / / /

mongomirror Changelog

On this page

  • mongomirror 0.12.8
  • mongomirror 0.12.7
  • mongomirror 0.12.6
  • mongomirror 0.12.5
  • mongomirror 0.12.4
  • mongomirror 0.12.3
  • mongomirror 0.12.2
  • mongomirror 0.12.1
  • mongomirror 0.12.0
  • mongomirror 0.11.2
  • mongomirror 0.11.1
  • mongomirror 0.10.0
  • mongomirror 0.9.1
  • mongomirror 0.9.0
  • mongomirror 0.8.0
  • mongomirror 0.7.0
  • mongomirror 0.6.0
  • mongomirror 0.5.2
  • mongomirror 0.5.1
  • mongomirror 0.5.0
  • mongomirror 0.4.1
  • mongomirror 0.4.0
  • mongomirror 0.3.1

Bug fixes:

  • Fixes an issue with handling timeseries databases.

  • Ignores the oplog entry with the startRangeDeletion identifier on the admin.system.version collection.

Bug fixes:

  • Fixes an issue where mongomirror would allow you to cut over to a MongoDB 4.2 destination cluster before the cluster was ready. The fix ensures that mongomirror waits for the index builds to complete on all cluster nodes during an initial sync before moving to oplog tailing and allowing you to start the cutover process.

Bug fixes:

  • Fixes an issue where mongomirror would ignore valid indexes as though they were duplicates due to ignoring options during index comparison.

Features and improvements:

  • Improves the retryability of transient connection issues.

Features and improvements:

  • Clarifies the error message that mongomirror returns when a collection exists on both the source and target cluster.

Bug fixes:

  • Fixes an issue where mongomirror returns the following error when it attempts to build an index for a namespace that is not present during an initial sync:

    Failed to record index build progress: namespace `` does not have a collection progressor

Bug fixes:

  • Fixes an issue handling large amounts of predated oplog entries.

  • Fixes a bug where initial sync would fail if the last oplog entry applied during initial sync was a transaction operation.

  • Fixes an issue where mongomirror detected resharding incorrectly, which caused false positives when checking the status of a reshard operation.

Bug fixes:

  • Fixes a connection issue introduced in mongomirror 0.12.0.

  • Fixes a bug where only one legacy index option is removed if two or more legacy index options exist for a collection on the source database.

  • Upgrades the Go driver to 1.7.1.

Bug fixes:

  • Fixes a connection issue introduced in mongomirror 0.12.0.

  • Reverts the Go driver to 1.5.4.

Features and improvements:

  • mongomirror now supports migrating time series collections.

  • New option --removeAutoIndexId to remove autoIndexId: false from collections that you migrate from MongoDB 3.6 or earlier.

  • mongomirror now fails when you attempt to migrate geoHaystack indexes to an Atlas cluster running MongoDB 5.0 or later.

  • mongomirror fails if a resharding operation occurs on the source cluster during a migration.

  • mongomirror now supports RHEL 8 on IBM zSeries platforms.

  • Upgraded Go driver to 1.6.

Features and improvements:

  • mongomirror binaries are now signed to ensure authenticity.

  • MongoDB now supports only the latest RHEL distribution on IBM zSeries platforms. These zSeries platforms are no longer supported:

    • rhel67-zseries-*

    • suse12-zseries-*

    • suse15-zseries-*

    • ubuntu1604-zseries-*

    • ubuntu1804-zseries-*

Bug fixes:

  • Fixes an issue with driver usage reporting in Atlas.

Features and improvements:

Bug fixes:

  • Improves sync status reporting.

  • Fixes slowness introduced in mongomirror 0.11.0.

Features and improvements:

  • New option --noIndexRestore to omit indexes when migrating data.

  • New option --awsSessionToken to authenticate with an AWS IAM role.

  • MongoDB v4.4 is now available as both a source and destination database version.

Bug fixes:

  • Improved error handling when a URI connection string is given for the --host option.

Features and improvements:

  • Improve initial sync performance for WiredTiger sources.

Features and improvements:

  • New --compressors option for network compression (enabled by default).

  • New --collStatsThreshold option to disable collStats when a specified number of collections is exceeded.

  • Build indexes for largest collections first.

  • Restart oplog buffering between collection copying and index building.

  • Improve oplog batch flushing to minimize small batches.

  • The default log level now logs when indexes start building.

Bug fixes:

  • Remove support for the --readPreference option. mongomirror must always read from the primary.

Features and improvements:

  • Initial sync inserts batch up to 100k documents instead of 1000.

  • Increase applyOps batch size.

Bug fixes:

  • Oplog buffering errors handling oplog entries over 16MB.

  • Disable socket timeout.

  • Initial sync client must not do primary detection for direct connections.

Features and improvements:

  • Upgrade to Go driver 1.1.1.

  • Add support for MongoDB 4.2.

  • Send writeConcern with collMod when the destination cluster is version 3.6+.

  • Remove legacy extended JSON usage.

Bug fixes:

  • Use direct connection to source cluster when replica set name isn't provided.

  • Authorization error on local database reading oplog from initial sync source.

  • Regression: non-transaction op processed as transaction op.

  • Catch QuitNotifier in applyOplogEntries.

  • Change lag calculation to avoid collection scans.

  • Oplog cursor is restarted instead of tailing on empty batch.


mongomirror version 0.6.0 was withdrawn and is no longer available.

MongoDB Support:

  • Adds support for MongoDB 4.2 as a destination only

Bug fixes:

  • Windows executable should have .exe suffix

Features and improvements:

  • Migrate and sync a subset of databases/collections (BETA)

  • Remove --tailOnly parameter

  • Now using the MongoDB Go driver

  • Upgrade to Go 1.12

Features and improvements:

  • Import collections in descending order of collection size to prevent one large collection from blocking completion.

  • Distinguish between can't connect and is not a replica set errors.

  • noCursorTimeout now prevents timeouts when syncing large collections.

Bug fixes:

  • Error while applying oplog entries to the destination: E11000 duplicate key error.

  • Recovery after CannotCreateIndex errors.

This release fixes a bug regarding bad index hints for capped collections.

This release adds the following features and improvements:

  • Support for buffering the oplog to disk during initial sync. This ensures that the source oplog will not run out of space during the migration process. For more information, see the documentation for the new --oplogPath command line option.

  • Use Go-native TLS on Windows (instead of OpenSSL 1.0.2n).

  • Upgrade to Go 1.11 (from 1.8).

  • mongomirror now removes the background flag from all indexes it creates. Background indexes created on the source cluster will be created as foreground indexes on the destination cluster. For more information on foreground index builds, see Index Build Operations on a Populated Collection.

This release fixes an installation error on some Windows hosts.

This release adds support for MongoDB 4.0 as both a source and destination for mongomirror.

This release adds the following features and improvements:

  • Support for MongoDB 4.0 as a destination only for mongomirror.

  • Support for tolerating elections and network errors on the destination during initial sync.

  • Support for syncing "system.js" collections.

  • Use Go-native TLS on MacOS (instead of OpenSSL 0.9.8).

  • mongomirror should ignore no-ops when reporting the latest oplog timestamp.

This release also removes support for Debian 7. Debian 7 is EOL and is not supported by MongoDB 4.0.

← mongomirror