Add a capability to set a timeout on the connection of mongos and mongod shards #1243
Conversation
This file contains 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
|
Sorry, I miss that latest release is 2.0.2. Please consider this patch for 2.0.2. |
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.
Hello, we faced the following problem: when one shard with mongod becomes unavailable ( connection is refused, e.g. a box is powered off; when mongos can't get some response from mongod within the adequate time), all mongoses from a shard cluster begin slowing down. It makes all mongos wait for some response from the dead shard. As result, all mongoses start timouting. This patch introduces a new parameter for mongos which allows to set a timeout on the connection between mongoses and shards.