Re: [grpc-io] Broken pipe errors in grpc client

2016-10-20 Thread Dinesh Pathak
Hi Vijay, We were facing these issues during some long running tests,
sending couple of TBs of data. Grpc was sending status code 13, which
according to code seems fatal, so we never tried.

/// Internal errors. Means some invariants expected by underlying System has
/// been broken. If you see one of these errors, Something is very broken.
INTERNAL = 13,

Thanks,
Dinesh

On Wed, Oct 19, 2016 at 4:04 AM, 'Vijay Pai' via grpc.io <
grpc-io@googlegroups.com> wrote:

> Do these error reports actually stop you from reusing this client? These
> are just log messages that say something about the underlying TCP
> connection, but they don't mean that it is a fatal failure on the channel.
> Note that gRPC automatically restarts the TCP connection if you are trying
> to send a message but there is no living TCP connection.
>
> On Friday, September 23, 2016 at 3:24:58 AM UTC-7, Dinesh Pathak wrote:
>>
>> Hi, Can someone help me with this question. Thanks.
>>
>> On Thu, Sep 22, 2016 at 8:46 AM, Dinesh Pathak 
>> wrote:
>>
>>> Both client and server are in cpp.
>>> Just to add, server is still usable after this and responds to requests
>>> if we make a new client.
>>>
>>> Thanks.
>>>
>>> On Thu, Sep 22, 2016 at 1:26 AM, Nathaniel Manista 
>>> wrote:
>>>
 On Tue, Sep 20, 2016 at 11:23 PM,  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","f
> ile_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?
 -Nathaniel

>>>
>>>
>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "grpc.io" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/grpc-io/1S3cNQTC-Zk/unsubscribe.
> To unsubscribe from this group and all its topics, 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 https://groups.google.com/d/
> msgid/grpc-io/dc818f17-d01c-4a1e-ab63-41a29a61d1af%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 
https://groups.google.com/d/msgid/grpc-io/CAHXyLKv7jTeWhm60ueEEO88RE20pBRiou73SXaEaJNT2Zu4PmA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [grpc-io] Broken pipe errors in grpc client

2016-10-18 Thread 'Vijay Pai' via grpc.io
Do these error reports actually stop you from reusing this client? These 
are just log messages that say something about the underlying TCP 
connection, but they don't mean that it is a fatal failure on the channel. 
Note that gRPC automatically restarts the TCP connection if you are trying 
to send a message but there is no living TCP connection.

On Friday, September 23, 2016 at 3:24:58 AM UTC-7, Dinesh Pathak wrote:
>
> Hi, Can someone help me with this question. Thanks.
>
> On Thu, Sep 22, 2016 at 8:46 AM, Dinesh Pathak  > wrote:
>
>> Both client and server are in cpp. 
>> Just to add, server is still usable after this and responds to requests 
>> if we make a new client.
>>
>> Thanks.
>>
>> On Thu, Sep 22, 2016 at 1:26 AM, Nathaniel Manista > > wrote:
>>
>>> On Tue, Sep 20, 2016 at 11:23 PM, > 
>>> 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?
>>> -Nathaniel
>>>
>>
>>
>

-- 
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 
https://groups.google.com/d/msgid/grpc-io/dc818f17-d01c-4a1e-ab63-41a29a61d1af%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [grpc-io] Broken pipe errors in grpc client

2016-09-23 Thread Dinesh Pathak
Hi, Can someone help me with this question. Thanks.

On Thu, Sep 22, 2016 at 8:46 AM, Dinesh Pathak  wrote:

> Both client and server are in cpp.
> Just to add, server is still usable after this and responds to requests if
> we make a new client.
>
> Thanks.
>
> On Thu, Sep 22, 2016 at 1:26 AM, Nathaniel Manista 
> wrote:
>
>> On Tue, Sep 20, 2016 at 11:23 PM,  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","f
>>> ile_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?
>> -Nathaniel
>>
>
>

-- 
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 
https://groups.google.com/d/msgid/grpc-io/CAHXyLKurDqSA9NZ-fRkabLOPQGGnK92Y%3DHQcaWHCF9Akjry4CQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [grpc-io] Broken pipe errors in grpc client

2016-09-21 Thread Dinesh Pathak
Both client and server are in cpp.
Just to add, server is still usable after this and responds to requests if
we make a new client.

Thanks.

On Thu, Sep 22, 2016 at 1:26 AM, Nathaniel Manista 
wrote:

> On Tue, Sep 20, 2016 at 11:23 PM,  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","f
>> ile_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?
> -Nathaniel
>

-- 
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 
https://groups.google.com/d/msgid/grpc-io/CAHXyLKvMZxq5Ruj%3DAq8ubxeTu-GmowqJe4HvLU5%2BXrrpJgDFvA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [grpc-io] Broken pipe errors in grpc client

2016-09-21 Thread 'Nathaniel Manista' via grpc.io
On Tue, Sep 20, 2016 at 11:23 PM,  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?
-Nathaniel

-- 
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 
https://groups.google.com/d/msgid/grpc-io/CAEOYnAT%2BG49rqTZ8G76rjfsDUO7Fn5w5D7nGGxtXKm_hVxU9Gg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


[grpc-io] Broken pipe errors in grpc client

2016-09-20 Thread dinesh
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.

-- 
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 
https://groups.google.com/d/msgid/grpc-io/c018e78e-a017-488e-9e1b-7e6a66bd2b03%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.