On Wed, Jun 21, 2017 at 3:10 AM, <[email protected]> wrote:
> Hi Eric, thanks for the response but i have to problems > 1) I am using grpc-java 1.0.1 which does not support this Interface (The > product team has decided on grpc version) > Sorry, but the feature wasn't available in 1.0.x. The only workaround in that case is to send "noop/trash" messages/RPCs periodically. Basically, TCP needs *writes* in order to discover *read* failures, so you generate noop writes on the TCP connection. If you receive GOAWAY from the server (like during server shutdown or server rotation), then any new RPCs will use a different connection, thus won't help you detect if the old connection is broken. Depending on your setup, that may not be much of a problem (e.g., if the server closes the connection soon after sending the GOAWAY). Using noop messages on the same RPC stream (by making it a bidi streaming RPC) wouldn't have that deficiency, but you'd also need to do the noop messages on all active streams and have to change more of your application logic. 2) The keepalive time is not fixed. > I don't understand this. Also i have a doubt about the whether grpc java 1.0.1 can support http2. I > found c based grpc 1.0.1 and grpc-java 1.0.1 has many different functions > I don't understand what you mean by functions. Could you explain more? It sounds like this is unrelated to the network break detection. -- 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]. 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/CA%2B4M1oOWzxOyyT%3D3_KcXqSR3tejsR7tSxedbbGmgT8d9Sw96YA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
smime.p7s
Description: S/MIME Cryptographic Signature
