Open Tanusyadav opened 3 months ago
Yes, as seen from
at io.grpc.netty.shaded.io.grpc.netty.NettyClientHandler$2.onGoAwayReceived(NettyClientHandler.java:284)
the server has sent a go away frame because it got terminated. You should check the gRPC server side to check the reason for the termination.
At the very least this should not be an INTERNAL error. GOAWAYs are normal and INTERNAL shouldn't be retried. With correct handling here, the RPC might even be able to be transparently retried on another connection and not expose any error to the application.
But v1.53.0 is pretty old (1.5 years old). You should try with a newer version.
But, but I also don't see a change to the important file to fix this. There's some other ways it could have been fixed though, and I'm surprised to see something like this today. So do try with a newer version and report back.
@Tanusyadav did you try with a newer version of gRPC-Java?
we've observed the following exceptions in our data pipeline and stopping the application:
Do we have a method to accurately know the cause of the failure? Is it due to the GRPC server? Is this internal error expected behavior? If not, any recommendation on how to avoid these exceptions? We're using (indirectly via spring-cloud-gcp-pubsub) and 1.53.0 gRPC version.