You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
we integrate client.go into our api-gateway.
when our backend gRPC server become unavailable,
our api-gateway process's cpu&memory&goroutines all goes up.
the problem is that client.go uses grpc.Dial() with grpc.WithBlock(),
so when server goes down, every call to grpcpool.getConn() will take 3-second to finish,
causing more and more goroutines got stuck at client.go#L104
The text was updated successfully, but these errors were encountered:
we integrate client.go into our api-gateway.
when our backend gRPC server become unavailable,
our api-gateway process's cpu&memory&goroutines all goes up.
the problem is that client.go uses
grpc.Dial()
withgrpc.WithBlock()
,so when server goes down, every call to
grpcpool.getConn()
will take 3-second to finish,causing more and more goroutines got stuck at client.go#L104
The text was updated successfully, but these errors were encountered: