Client became DEAD when server down right after request sent

[咚不龙咚强]

Hi,

  I'm a fan of grpc. Here's the issue I found.

  As per my understanding, a client call will send confirming message first to confirm server is available, then send out the request. What if a client call got acknowledged that server is ready and request sent, while suddenly server got down just before server send a response. I tried such case, as a result, client became DEAD, thread blocked. 

  Is that a issue? How can I avoid this?

  Expecting your reply.

  Thanks

  Ted

[Carl Mastrangelo]

You need to add a Deadline to your RPC to make sure it eventually fails.  

[咚不龙咚强]

Gotcha. CallOptions. I should read docs/examples more carefully. Thanks. 

------------------ 原始邮件 ------------------

发件人: "Carl Mastrangelo";<not...@google.com>;

发送时间: 2017年2月9日(星期四) 凌晨0:55

收件人: "grpc.io"<grp...@googlegroups.com>;

抄送: "咚不龙咚强"<4923...@qq.com>;

主题: Re: Client became DEAD when server down right after request sent

[咚不龙咚强]

Hi,

  As per about page, grpc support "Connecting mobile devices, browser clients to backend services". But I can't find a pure javascript impl(lib like grpc.js). Actually, I want to use in such way as http://thrift.apache.org/lib/js. Can you suggest? Thanks.