Repository navigation
fix(rpc): apply RST_STREAM frame limit by default #7015
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
waynercheung
wants to merge
1
commit into
tronprotocol:release_v4.8.3
Choose a base branch
from
waynercheung:fix/rpc-rst-stream-limit
base: release_v4.8.3
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[DISCUSS] This bounds RST_STREAM per connection, but not per client. grpc-netty creates a new
RstStreamCounterfor each connection (NettyServerTransport#L144 → NettyServerHandler#L268-L269) and, on overflow, closes only that connection withENHANCE_YOUR_CALM "too_many_rststreams"(#L590-L594). The gRPC ports have no per-IP connection cap: there is noServerTransportFilterand no TLS,maxConnectionsWithSameIpis P2P-only, andRateLimiterInterceptorruns per call, after the stream already exists. A client that reconnects after each GOAWAY therefore keeps much of its stream-creation rate; in a loopback test, reconnecting under 1000/5 still kept more than half of the unlimited rate. The javadoc itself says the setting "can reduce the impact … when combined with TLS and maxConcurrentCallsPerConnection".This is still a clear improvement and needs no code change here. Could the upgrade note say that a reconnecting client is not bounded, and recommend connection-rate or per-IP limits at the LB/firewall for public gRPC ports? A per-IP gRPC connection cap could go under "Follow up".