INTERNAL error in src/core/lib/iomgr/tcp_posix.c:340

[Yaz Saito]

I've got a long-running streaming RPC that failed with grpc INTERNAL error,

GRPC error INTERNAL: {\"created\":\"@1484819778.633679016\",\"description\":\"OS Error\",\"errno\":32,\"file\":\"src/core/lib/iomgr/tcp_posix.c\",\"file_line\":340,\"os_error\":\"Broken pipe\",\"syscall\":\"sendmsg\"}"

So it looks like grpc returns INTERNAL on EPIPE. 

Is INTERNAL error ever supposed to be returned to the application? The document seems to suggest otherwise. Shall the application blindly treat INTERNAL as UNAVAILABLE?

--

yaz

[Ken Payson]

In general, INTERNAL errors may be returned to the application, but unlike UNAVAILABLE are not retryable.

The EPIPE issue you are seeing is a bug that was addressed here, and should be returned as an UNAVAILABLE error in the next release.

--
You received this message because you are subscribed to the Google Groups "grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email to grpc-io+unsubscribe@googlegroups.com.
To post to this group, send email to grp...@googlegroups.com.
Visit this group at https://groups.google.com/group/grpc-io.
To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/CALsnwnLWxajTGg6jskRHn%2B2P5qzZ%2B0BgQy0Y9z3bE3AoofdLFw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Yaz Saito]

Ok, thanks for the update.

--

yaz