Reverted replicaSetName in favor of putting more hosts in connection string #273
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Author
fealebenpae
approved these changes
Jul 18, 2025
lsierant
requested review from
anandsyncs and
viveksinghggits
and removed request for
a team
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
This reverts handling replicaSetName from mongot config and adds passing all mongod hosts in the connection string.
It is not necessary now to set it, as mongot is connecting in a replicaset mode when there is more than one host passed on connection string.
Proof of Work
Based on PR #229
Chain of upstream PRs as of 2025-07-17
PR Search Public Preview - main feature branch #229:
master←search/public-previewsearch/public-preview←lsierant/search-multiple-hosts