On Thu, Jun 23, 2016 at 8:13 AM, mouse <[email protected]> wrote: > 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. >
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 <https://github.com/grpc/grpc/issues/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 -- 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 [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/CAEOYnASBoWemZ3DNvc9BcNu8JancFX09nb9US3%2BSCug105X9GQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
