How can the client automate the handling of the GOAWAY signal?

[SpecialYang]

I am using the go grpc client. When the server sent the go away frame to client, the grpc client just throw error but not do anything. How can the client automate the handling of the GOAWAY signal to reconnect?

[zasweq]

Our GOAWAY handling is described in this RFC: https://httpwg.org/specs/rfc7540.html#rfc.section.6.8. When the server sends the first GOAWAY, it usually gives some time to the client to terminate the connection gracefully, before sending the second GOAWAY (at which point, the connection is hard closed). When the connection gets hard closed, the Channel can retry connecting at that point. Our built in client HTTP/2 transport handles these GOAWAY frames already (see https://github.com/grpc/grpc-go/blob/master/internal/transport/http2_client.go#L855).

[SpecialYang]

But I receive the following error.

rpc error: code = Internal desc = stream terminated by RST_STREAM with error code: NO_ERROR

Seems like the grpc client doesn't resolve the GOAWAY. I can't find any reason. Please help me.

[SpecialYang]

@zasweq Sorry for ping. Could you help me to solve the above error? I can't find why this error will happen.

[dfawley]

@SpecialYang Is the server you're talking to gRPC-Go? Can you give more data?

The client will reconnect when this happens. But the RPC has failed, and there's no way to prevent this from the client side. You'll need to retry the RPC. We can't do this automatically once the stream has been started, because it could be unsafe depending on the specific RPC's behavior.

[github-actions]

This issue is labeled as requiring an update from the reporter, and no update has been received after 6 days. If no update is provided in the next 7 days, this issue will be automatically closed.