Connection Pool Querytimeout Support #188
Merged
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
mfenniak
added a commit
that referenced
this pull request
Dec 13, 2014
Query timeout configuration support for pooled connections
|
Hey Lucas, this looks great. Thanks for the contribution. 👍 |
mfenniak
added a commit
that referenced
this pull request
Dec 13, 2014
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.
In our application we use RethinkDb for some analysis queries. They can be very slow. Unfortunately as is there is no way to manipulate the timeout when using a connection pool. This adds a parameter in the connectionPool element in the web.config.
<connectionPool enabled="true" queryTimeout="300" />Would extend the timeout to 5 minutes.