RUBY-949 Initialize topologies to Unknown and discover standalones #641
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
estolfo
force-pushed
the
RUBY-949-single-mongos
branch
from
5d439c0 to
97d1b50
Compare
estolfo
force-pushed
the
RUBY-949-single-mongos
branch
from
97d1b50 to
bc98ba9
Compare
estolfo
added a commit
that referenced
this pull request
Jun 24, 2015
RUBY-949 Initialize topologies to Unknown and discover standalones
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This pull request adds a StandaloneDiscovered event and always sets a topology to Unknown if :connect is not explicitly specified.
This will allow a Cluster Topology to be set to Sharded in the case that a single mongos is discovered.