Kannan J
Kannan J
There is not much in these logs. We need logs like in this comment [here](https://github.com/grpc/grpc-java/pull/12207#issuecomment-3074459371) with details about the netty streams.
> [@kannanjgithub](https://github.com/kannanjgithub) Hi, from the grpc logs mentioned above, does the logs as "INBOUND DATA" mean that the response data from the server has been transferred to the grpc-core, such...
Creating connections at startup vs lazy depends on the use case, obviously creating them at startup incurs some network and CPU cost if there are no RPCs. To keep connections...
Yes, if the gRPC client detects the connection to be broken via the absence of responses to the ping frames, it will close the connection and it reconnect if a...
Yes, that is correct.
Connection reset will cause a TRANSIENT_ERROR for the channel and it will be retried with exponential backoff. The retry policy, including backoff parameters (initial backoff, max backoff, backoff multiplier), retryable...
Agree, there is a need to handle the trailers in a better way here.
The max inbound message size is for the whole of the gRPC message. The flow control error reported here occurs when the sender (client in this case) sends a frame...
It is possible that an intermediate proxy overshoots the flow control window and the server resets the stream and the proxy propagates the error back to the gRPC client. Is...