Skip to content

Set grpc.http2.min_ping_interval_without_data_ms to 5s to avoid too_many_pings#6

Open
jmthomas wants to merge 1 commit intoanycable:mainfrom
jmthomas:pings
Open

Set grpc.http2.min_ping_interval_without_data_ms to 5s to avoid too_many_pings#6
jmthomas wants to merge 1 commit intoanycable:mainfrom
jmthomas:pings

Conversation

@jmthomas
Copy link
Copy Markdown

Summary

Per https://github.com/grpc/grpc/blob/master/doc/keepalive.md and grpc/grpc#25713 it is tricky to get the keep alive ping setting correct. In our own application using anycable I've seen the following errors:

2026/04/24 18:33:39 ERROR: [transport] Client received GoAway with error code ENHANCE_YOUR_CALM and debug data equal to ASCII "too_many_pings".

This seemed to have improved over time so I don't know if some of the settings have changed but I think it is still incorrect. Based on a lot of reading it appears the server minimum has to be strictly lower than the client interval or jitter produces strikes. You had them set exactly the same. Since the client is hard coded to 10 I set the server to 5.

More information is available here: https://github.com/grpc/proposal/blob/master/A8-client-side-keepalive.md

Also I remove the key that had no effect. The key that matters is grpc.http2.min_ping_interval_without_data_ms as documented here: https://grpc.github.io/grpc/core/group__grpc__arg__keys.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant