Skip to content

Conversation

@basclaessen
Copy link

No description provided.

@linux-foundation-easycla
Copy link

linux-foundation-easycla bot commented Jan 23, 2026

CLA Signed

The committers listed above are authorized under a signed CLA.


Keepalive PINGs are only sent when the HTTP/2 connection did not receive data for `KEEPALIVE_TIME`.

L7 load balancers may be configured to load balance the HTTP/2 streams inside the HTTP/2 connection to different servers. Although HTTP/2 PINGS are forwarded in both directions by the L7 load balancer unexpected connection drops can occur because a keepalive PING is not sent.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

HTTP/2 PINGs aren't forwarded by L7 load balancers. PING is point-to-point, so the LB would need to do its own PINGs to backends if that is what it desires.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I removed the forwarding part from the proposal.
The example in the proposal is a real example. I 'solved' this L7 load balancer behavior by implementing a fixed keepalive interval.
I think the real question is if the grpc team wants to implement this kind of features to compensate bad implemented/configured load balancers.
I can perfectly understand that you do not want to do this.

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.

2 participants