Hi Kun,
I did see that the new server3 (listening on 9097) has its
InternalSubchannel gets created:
[io.grpc.internal.InternalSubchannel] (grpc-default-worker-ELG-3-9)
[io.grpc.internal.InternalSubchannel-20]
io.grpc.netty.NettyClientTransport-21 for localhost/127.0.0.1:9097 is ready
[io.grpc.internal.InternalSubchannel] (grpc-default-worker-ELG-3-9)
[io.grpc.internal.InternalSubchannel-20]
io.grpc.netty.NettyClientTransport-21 for localhost/127.0.0.1:9097 is ready
On Wednesday, January 9, 2019 at 10:18:47 AM UTC-8, eleano...@gmail.com
wrote:
>
> Hi,
>
> in my java gRPC client, when I create the ManagedChannel, I am passing my
> custom NameResolver, and using RoundRobinLoadBalancer. When my NameResolver
> is notified with a change to the server list (new server added), it will
> call Listener.onAddress and pass the updated the list.
>
> I see from the Log: the onAddress is called from NameResolverListenerImpl,
> (9097 is the new server address added)
>
> resolved address: [[addrs=[localhost/127.0.0.1:9096], attrs={}],
> [addrs=[localhost/127.0.0.1:9097], attrs={}]], config={}
>
>
> however, the traffic is not coming to the new server, did I miss anything?
>
>
> Thanks a lot!
>
>
>
>
>
>
--
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@googlegroups.com.
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/8ac923ac-0dd1-4165-8fde-859635c37678%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
