You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Clarify reporting of change events in progress logs. (#24)
A few things can cause migration-verifier to recheck a document:
1. document is mismatched between source & destination
2. document is missing on source or destination
3. document changed on source and needs a recheck
Unfortunately, the verifier’s metadata persists 2 and 3 together, such that the verifier’s progress logs can’t differentiate them. The current progress logs, though, report them all as “missing”, which can confuse users.
This changeset updates the logging verbiage to be clearer that the “missing documents” totals are really “missing or changed documents”.
Copy file name to clipboardExpand all lines: README.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -269,6 +269,8 @@ The migration-verifier is also rather resource-hungry. To mitigate this, try lim
269
269
270
270
- The verifier, during its first generation, may report a confusing “Mismatches found” but then report 0 problems. This is a reporting bug in mongosync; if you see it, check the documents in `migration_verification_metadata.verification_tasks` for generation 1 (not generation 0).
271
271
272
+
- The verifier conflates “missing” documents with change events: if it finds a document missing and receives a change event for another document, the verifier records those together in its metadata. As a result, the verifier’s reporting can cause confusion: what its log calls “missing or changed” documents aren’t, in fact, necessarily failures; they could all just be change events that are pending a recheck.
273
+
272
274
# Limitations
273
275
274
276
- The verifier’s iterative process can handle data changes while it is running, until you hit the writesOff endpoint. However, it cannot handle DDL commands. If the verifier receives a DDL change stream event (drop, dropDatabase, rename), the verification will fail. If an untracked DDL event (create, createIndexes, dropIndexes, modify) occurs, the verifier may miss the change.
0 commit comments