Default single-node connstrs to direct connection; improve docs #143
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
mongosh defaults single-node connections to a direct connection. This changeset applies that logic to migration-verifier so that, if a connection string includes only a single node, the verifier will always connect to it.
This is useful, e.g., when using a single, containerized mongod for the metadata DB and the mongod’s replication is set up to reference its hostname. In that case a direct connection is necessary when using Podman or other container engines that don’t “inject” the container name into the host’s name resolution (as, e.g., Docker Desktop on macOS does).
At the same time, this changeset avoids the above problem by explicitly making the documentation’s container one-liner bind to
localhost.