Releases: mongodb-labs/migration-verifier
Releases · mongodb-labs/migration-verifier
v0.1.0
v0.1.0
Bug fixes:
- REP-6873: Handle a “nil” resume token on startup.
- Prevent logs from missing changes that happen “between” generations.
(This is purely a logging fix.) - Prevent /progress from reporting 0 tasks for generation 0.
New features:
- REP-6797: The metadata can now be stored on a standalone mongod.
(Previously replication was required, even for a single node.) - Logs now track mismatch “duration”, i.e., the amount of time that
has passed when a mismatch remains. This helps to highlight
mismatches prior to cutover. - Logs now show the optime of the latest change event whose recheck
has been completed. This gives an at-a-glance indicator of Verifier’s
progress relative to both source & destination cluster times. - Verifier can now track changes by reading the oplog rather than
using a change stream. Reading the oplog is generally faster but
carries some important caveats. See documentation.
v0.0.13
v0.0.13
- Fix a panic when failing to load resume token.
- Ignore MongoDB-internal databases.
- Update x/crypto.
v0.0.12
v0.0.12
- REP-6832: This fixes document fetches always to use the cluster’s most
recently-seen timestamp, and to use majority read concern. Previously
document fetches used local read concern and sent only the start time
as the afterClusterTime, which allowed stale or not-majority-committed
data to be used in comparisons.
v0.0.11
v0.0.11
- REP-6804 (BUG FIX): This fixes potential skipped rechecks after a mismatch.
v0.0.10
v0.0.10
- REP-6785 (BUG FIX): This prevents skipped documents across a restart
of the verifier. - Verification is now uses CPU and metadata much more efficiently.
This allows verification of migrations that previously exceeded
the verifier’s abilities. - Single-node connection strings now default to a direct connection.
v0.0.9
v0.0.9
This release fixes a recently-introduced bug that caused a failure on
startup if srcURI or dstURI were specified in a config file but not as
command arguments.
v0.0.8
v0.0.8
- BUG FIX: Statistics aggregation failed when a recheck included collection
metadata. - Add basic time-series support. See documentation for important caveats.
v0.0.7
v0.0.7
- BREAKING CHANGE: Replace the --debug parameter with --logLevel.
- Add a --start CLI parameter.
- Reduce generation-end pause.
- Add a download script.
- Optimize change stream reading.
- Move a few overly-prolix log messages to trace-level.
- Various small improvements.
v0.0.6
v0.0.6
This release optimizes the handling of change streams. These changes will
help verification to keep pace with cluster writes.
v0.0.5
v0.0.5
- REP-6438: Logs now reflect progress made in currently-running tasks.
- REP-6492: Partitioning will now, when possible, use an algorithm that
divides collections more evently.