Bump spdystream to v0.5.0 to resolve memory leaks on remotecommand.NewSPDYExecutor
#224
Conversation
This file contains hidden or 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
yimgzz
force-pushed
the
bump-spdystream
branch
from
1fa3fe0 to
6dbeb40
Compare
yimgzz
force-pushed
the
bump-spdystream
branch
from
6dbeb40 to
8d5b748
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
All Submissions:
closes #XXXXin your comment to auto-close the issue that your PR fixes (if such).When working with the tarantool operator found unusually RAM usage and during investigation of the problem found cause - it was
remotecommand.NewSPDYExecutor:Related issues:
moby/spdystream#92
kubernetes/kubernetes#105830
Update spdystream to v0.5.0 fixed memory leaks on controller pod