Never reject free-context style transport requests #123039
Open
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
These things cost effectively nothing in terms of heap or during handling but their handling actually does free memory. They should never be rejected. Otherwise a storm of 429s might lead to some sticky memory consumption until the contexts time out. We wouldn't see this currently as we don't log any warnings (just debug+trace level messages here) if freeing a context fails.
original-brownbear
added
>non-issue
:Search Foundations/Search
elasticsearchmachine
added
the
Team:Search Foundations
|
Pinging @elastic/es-search-foundations (Team:Search Foundations) |
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.
These things cost effectively nothing in terms of heap or during handling but their handling actually does free memory. They should never be rejected. Otherwise a storm of 429s might lead to some sticky memory consumption until the contexts time out.
We wouldn't see this currently as we don't log any warnings (just debug+trace level messages here) if freeing a context fails.