Closed Tanusyadav closed 7 months ago
I'm surprised to see that error reported to the client. "Stream closed before write could take place" generally means a cancellation or deadline occurred. But when the stream closed we should have reported an error to the client. Later, any pending writes are cancelled, and sometimes those show up in logs which is annoying but benign. But here it is showing up as the RPC status, which is weird.
What version of gRPC are you using?
I will close this bug since we haven't heard back, but we can open it up again if needed.
@ejona86 We are using 1.53.0 gRPC version
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 client or the GRPC server? Is this internal error expected behaviour? If not, any recommendation on how to avoid these exceptions?