-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
fix(grpcproxy): add missing GRPCKeepAliveEnforcementMinimum #15708
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## master #15708 +/- ##
==========================================
- Coverage 49.67% 49.66% -0.01%
==========================================
Files 267 267
Lines 46383 46388 +5
==========================================
Hits 23039 23039
- Misses 21084 21089 +5
Partials 2260 2260
☔ View full report in Codecov by Sentry. |
the absence of the setting potentially causes ENHANCE_YOUR_CALM Signed-off-by: phanama <[email protected]>
a441f1f
to
c967706
Compare
The local grpcproxy is also missing some other server parameters, in particular these three: Lines 729 to 731 in ef88d1d
I'll leave it in separate community discussion, whether or not these are needed in the local grpcproxy. |
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.
Looks good, @crenshaw-dev should we consider backporting this commit? Realistically they should have the minimums enforced.
Related to #15707 |
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.
LGTM!
@ishitasequeira Thank you! Can we cherrypick this bugfix into v2.8, v2.7, and v2.6? |
the absence of the setting potentially causes ENHANCE_YOUR_CALM Signed-off-by: phanama <[email protected]> Co-authored-by: Dan Garfield <[email protected]>
the absence of the setting potentially causes ENHANCE_YOUR_CALM Signed-off-by: phanama <[email protected]> Co-authored-by: Dan Garfield <[email protected]> Signed-off-by: jmilic1 <[email protected]>
@ishitasequeira @todaywasawesome Hi Ishita and Dan! 👋 Since this still bites us in production that affects hundreds of our engineers and updating this on our argo dependency will be a much easier fix than disabling Thank you lots in advance! 🙂 |
Good call, We can do that. I'll take it on. |
@todaywasawesome sincerely apologize for the nudge, any update on this? 🙂 |
Oh thanks for the reminder, I'll do today. |
/cherry-pick release-2.8 |
/cherry-pick release-2.7 |
the absence of the setting potentially causes ENHANCE_YOUR_CALM Signed-off-by: phanama <[email protected]> Co-authored-by: Dan Garfield <[email protected]>
…#15708) the absence of the setting potentially causes ENHANCE_YOUR_CALM Signed-off-by: phanama <[email protected]> Co-authored-by: Dan Garfield <[email protected]>
…#15708) the absence of the setting potentially causes ENHANCE_YOUR_CALM Signed-off-by: phanama <[email protected]> Co-authored-by: Dan Garfield <[email protected]> Signed-off-by: Maxime Brunet <[email protected]>
…16576) the absence of the setting potentially causes ENHANCE_YOUR_CALM Signed-off-by: phanama <[email protected]> Signed-off-by: Maxime Brunet <[email protected]> Co-authored-by: Yudi A Phanama <[email protected]> Co-authored-by: Dan Garfield <[email protected]>
the absence of the setting potentially causes ENHANCE_YOUR_CALM Signed-off-by: phanama <[email protected]> Co-authored-by: Dan Garfield <[email protected]>
the absence of the setting potentially causes ENHANCE_YOUR_CALM Signed-off-by: phanama <[email protected]> Co-authored-by: Dan Garfield <[email protected]>
the absence of the setting potentially causes ENHANCE_YOUR_CALM Signed-off-by: phanama <[email protected]> Co-authored-by: Dan Garfield <[email protected]>
Can we get a release for 2.6/2.7/2.8 series with this fix? It would be most appreciated. |
the absence of the setting potentially causes ENHANCE_YOUR_CALM Signed-off-by: phanama <[email protected]> Co-authored-by: Dan Garfield <[email protected]>
The keepalive
MinTime
parameter with valueGRPCKeepAliveEnforcementMinimum
is missing from apiclient's local grpcproxy when usingGrpcWeb=true
. This causesENHANCE_YOUR_CALM
errors for long-running requests taking >80s, due to the client having lower ping interval value (20s) than the local grpcproxy server's (default 5m ref). See grpc keepalive doc.The same parameter was added in #9922 but probably was skipped in the grpcproxy implementation.
Fixes: #15707
Checklist: