how to hold grpc client error

77 views
Skip to first unread message

mouse

unread,
Jun 23, 2016, 11:13:29 AM6/23/16
to grpc.io
With using grpc, If server is not in serving, client will try to connect again and again. like that

E0623 23:00:55.347071102    9431 tcp_client_posix.c:191]     failed to connect to 'ipv4:101.201.77.240:50052': timeout occurred
E0623 23:01:01.860252293    9431 tcp_client_posix.c:191]     failed to connect to 'ipv4:101.201.77.240:50052': timeout occurred
E0623 23:01:13.193809141    9431 tcp_client_posix.c:191]     failed to connect to 'ipv4:101.201.77.240:50052': timeout occurred

I even cannot break it by ctrl +c.  I must find out the pid and then kill it.

I want it throw a exception, I could catch it and then return or do something else, rather than try to connect again and again. 

Nathaniel Manista

unread,
Jun 23, 2016, 12:26:50 PM6/23/16
to mouse, grpc.io
In what language are you working? I suspect Python from other communication you've had with us but please confirm?

It sounds like you're hitting bug 4148. This defect was present in gRPC 0.14 but has been fixed and will not be present in gRPC 0.15. We hope to release 0.15 in the next seven days.
-Nathaniel

mouse

unread,
Jun 23, 2016, 6:32:15 PM6/23/16
to grpc.io, runm...@gmail.com
the server is python and the client is also python.

在 2016年6月24日星期五 UTC+8上午12:26:50,Nathaniel Manista写道:
Reply all
Reply to author
Forward
0 new messages