Skip to content

Commit 306ad47

Browse files
authored
Merge pull request #5 from mongodb-labs/readme_update_sep_2023
Update the README for known issues & limitations.
2 parents 632624b + 03e2cff commit 306ad47

File tree

1 file changed

+12
-4
lines changed

1 file changed

+12
-4
lines changed

README.md

Lines changed: 12 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -94,10 +94,6 @@ The verifier will now check to completion to make sure that there are no inconsi
9494
`{"progress":{"phase":"idle","error":null,"verificationStatus":{"totalTasks":1,"addedTasks":0,"processingTasks":0,"failedTasks":1,"completedTasks":0,"metadataMismatchTasks":0,"recheckTasks":0}}}`
9595
9696
97-
# Limitation
98-
99-
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.
100-
10197
# Benchmarking Results
10298
10399
Ran on m6id.metal + M40 with 3 replica sets
@@ -220,3 +216,15 @@ Any collection metadata mismatches will occur in a task with the type '`verifyCo
220216
221217
222218
In this case, '`failed_docs`' contains all the meta data mismatches, in this case an index named '`x_1`'.
219+
220+
# Known Issues
221+
222+
- The verifier may report missing documents on the destination that don’t actually appear to be missing (i.e., a nonexistent problem). This has been hard to reproduce. If missing documents are reported, it is good practice to check for false positives.
223+
224+
- 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).
225+
226+
# Limitations
227+
228+
- 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.
229+
230+
- The verifier crashes if it tries to compare time-series collections. The error will include a phrase like “Collection has nil UUID (most probably is a view)” and also mention “timeseries”.

0 commit comments

Comments
 (0)