[grpc-io] `Connection failed` issue after some successful calls

Hi, I am using gRPC on nodejs. I am able create a new client and call rpc methods successfully but after some time, it is throwing me 'Connection failed` error. from *rpc-client.js *file import grpc from 'grpc' const package = grpc.load(PROTO_PATH).external.protocol const client = new

Re: [grpc-io] Asynchronous Basics question

stream is part of your API definition while sync/async is about implementation. You should decide whether to have "stream" according to whether you can have more than one reply messages. As you said, whether to use async or sync implementation is about your resource limitations. If you have a

Re: [grpc-io] Re: How do I run grpc/test ?

Hi Yang, Thanks for the response. I figured that out and debugging the server and client helped me a lot to understand the architecture. On Friday, June 16, 2017 at 4:08:10 PM UTC-4, Yang Gao wrote: > > You can make fling_client fling_server and look at fling_test.c to see how > to run them

Re: [grpc-io] Re: How do I run grpc/test ?

You can make fling_client fling_server and look at fling_test.c to see how to run them manually. On Tue, Jun 13, 2017 at 9:02 AM, Rajarshi Biswas wrote: > Hi Guys, > > So I figured I have to make this using bazel ? But I get the following > error now. > > bazel

[grpc-io] T.eh. Ret w w et nmr

Sent from my iPhone -- 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] [gRPC-go]use multi-addrConn to same endpoint

here is gateway as gRPC-go client to proxy all request to gRPC server , In high concurrency or high QPS benchmark, addrConn soon reach the limitation of number of concurrent HTTP2 streams (e.g. 1000) though clientConn is multiplexed . Is any best practice about handle multi-addrConn to