On Tuesday, 31 July 2018 20:30:41 UTC+2, Carl Mastrangelo wrote:
> There will be upcoming documentation on the exact way to configure this,
> but this is being announced here for interested parties to try it out and
> answer any questions.
>
(...) and there currently isn't a load reporter. I
Do i need to create my own loadbalancer or can i use the RoundRobin
> NettyChannelBuilder.forTarget(rpcTarget)
> .loadBalancerFactory(RoundRobinLoadBalancerFactory.getInstance())
> .nameResolverFactory(DnsNameResolverProvider.asFactory())
>
Thanks a lot for the clarification
On Friday, August 17, 2018 at 12:29:15 PM UTC-7, Carl Mastrangelo wrote:
>
> Yes, that is correct. Load Balancing is done on a per-call basis. Once
> an RPC has been assigned to a backend, it will continue on that backend.
>
> On Friday, August 17, 2018 at
Yes, that is correct. Load Balancing is done on a per-call basis. Once
an RPC has been assigned to a backend, it will continue on that backend.
On Friday, August 17, 2018 at 9:20:02 AM UTC-7, eleano...@gmail.com wrote:
>
> Hi,
>
> I just wonder how does gRPC LB handles the bi-directional
Hi,
I just wonder how does gRPC LB handles the bi-directional stream? Once it
picks which server instance to serve the streaming request, then it will
continue the streaming request only with that particular server?
On Tuesday, July 31, 2018 at 11:30:41 AM UTC-7, Carl Mastrangelo wrote:
>
>
