From ffb7e37b3e6e035e7c05c395f8e2311d3f02272d Mon Sep 17 00:00:00 2001 From: Maria van Keulen Date: Fri, 5 Dec 2025 14:35:43 -0500 Subject: [PATCH] Remove note on storing metadata on destination cluster This is not recommended for performance reasons, so we should remove mention of it. --- README.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/README.md b/README.md index 48926001..3de283f7 100644 --- a/README.md +++ b/README.md @@ -36,8 +36,6 @@ migration-verifier needs a MongoDB cluster to store its state. This cluster *mus See [above](#Quick-Start) for a one-line command to start up a local, single-node replica set that you can use for this purpose. -The verifier can alternatively store its metadata on the destination cluster. This can severely degrade performance, though. Also, if you’re using mongosync, it requires either disabling mongosync’s destination write blocking or giving the `bypassWriteBlockingMode` to the verifier’s `--metaURI` user. - # More Details To see all options: