On Tue, Sep 20, 2016 at 11:23 PM, <din...@cohesity.com> wrote:

> Hi, While running grpc client, sometimes we are getting "broken pipe" and
> "connection reset by peer" errors. Frequency is pretty less.
> Should not grpc client itself retry on these errors.
> What is the application supposed to do in these cases? Is it ok to just
> retry the request in application or do we need to reinitialize the client?
> I am using grpc v1.0.
> {"created":"@1474401100.638932982","description":"OS
> Error","errno":32,"file":"src/core/lib/iomgr/tcp_posix.c","
> file_line":340,"os_error":"Broken pipe","syscall":"sendmsg"}
> {"created":"@1474368842.846383126","description":"OS
> Error","errno":104,"file":"src/core/lib/iomgr/tcp_posix.
> c","file_line":340,"os_error":"Connection reset by
> peer","syscall":"sendmsg"}
> Thanks in advance.

With what programming language are you using gRPC?

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+unsubscr...@googlegroups.com.
To post to this group, send email to grpc-io@googlegroups.com.
Visit this group at https://groups.google.com/group/grpc-io.
To view this discussion on the web visit 
For more options, visit https://groups.google.com/d/optout.

Reply via email to