Revert "Preserve the caller's stacktrace for blocking API (#2420)" #2488
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
This reverts commit 8b41bf4.
daschl
approved these changes
Jan 12, 2023
idelpivnitskiy
added a commit
that referenced
this pull request
Jan 24, 2023
…2488) This reverts commit 8b41bf4. Motivation: There are cases when Netty's DNS resolver may put an exception into the cache and return it multiple times. In this case, we keep adding suppressed exceptions to the same instance and it leads to a memory leak and increased logging output. Let's revert this feature before the upcoming release and revisit later when we figure out the approach for Netty/ST DNS resolver.
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.
This reverts commit 8b41bf4.
There are cases when Netty's DNS resolver may put an exception into the cache and return it multiple times. In this case, we keep adding suppressed exceptions to the same instance and it leads to a memory leak and increased logging output.
Let's revert this feature before the upcoming release and revisit later when we figure out the approach for Netty/ST DNS resolver.