Hi Eric, Thanks for checking this. Sorry if this is a duplicate response. Not sure if the last message reached as my machine shutdown just as I hit the send
I'm analysing on using grpc keep alive to detect dangling connections between my client and server like hardware failure or something similar which brings down the server and the connection doesn't get closed. This is helping me in case I don't use a proxy in between my services. And as you said istio side car is responding to h2 pings from my clients, I modified ip tables of my server to simulate a blackhole kind of scenario and my client was still sending those h2 pings and getting back ack for it Do you have a suggestion on what I can do to make sure my client detects these kinds of broken servers? Right now all the calls are unary between them On Monday, September 29, 2025 at 8:00:18 PM UTC+5:30 Eric Anderson wrote: > On Mon, Sep 29, 2025 at 7:22 AM Prathish Elango <[email protected]> > wrote: > >> BUT I dont see the reverse of this in my server logs. It has also io.grpc >> trace logs enabled. I don't see the INBOUND PING with ack=false and >> OUTBOUND PING with ack=true in my server logs >> >> And I don't see GO_AWAY also if permitkeepalive threshold is greater than >> my keepalive time. >> > > That's because the keepalive is limited to the HTTP/2 connection. It can > go through L4/TCP proxies, but Istio will have an L7 proxy. So you're doing > keepalive between the client and the sidecar. For what are you wanting to > use keepalive? > -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/grpc-io/7f67d5d6-e30d-4a4a-9027-f73cc9f7c7acn%40googlegroups.com.
