Refactor TimeoutPoller into SQLServerTimeoutManager #913
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
needs test cases
fix formatting as well
…ng timeouts and infinite polling checking for timeouts Specifically in microsoft#842, I introduced a single thread to replace the infinite timeout thread pool. However the thread lives forever, so this change seeks to fix that. Also the interrupt logic before/after my change can block timeout threads. So this change also addresses that.
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.
As discussed in #909, we need to address the edge case where the timeout thread lives forever even after all the connections are closed and the classloader tries to unload the driver package.
Also addressed is the handling blocking interrupt calls within the timeout functionality