Hi team,
I’m not sure whom to reach out to regarding a question about a gRPC version upgrade. Earlier, I was using gRPC version *1.68.3*. In that version, regardless of the type of client disconnection — 1. Client reload 2. Client flapping 3. Client power-off — the onError callback was being invoked. After upgrading to *gRPC version 1.73.0*, onError is no longer being called for any of these disconnection scenarios. I have been able to handle scenarios #1 and #2 using a ServerTransportMonitor, but I am not able to handle scenario #3 (client power-off from the switch). Is this a known change or a regression? I’m curious to understand why this behavior has changed with the version upgrade. Thanks in advance for your help. Best regards, Vasanth -- 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/276db53b-1aad-4660-a81e-1a146b474d48n%40googlegroups.com.
