Like Penn said, you can turn it on (it's experimental), but will eventually be replaced. The flag itself is pretty simple, but the rest of the machinery needs to be set up properly for it to work. We (gRPC maintainers) are not comfortable supporting this yet, hence the extra effort to turn it on. The gRPCLB Load Balancer is experimental, so we will likely remove it at some point. We will give a notice in one of the upcoming releases that it is deprecated, and then remove it the release after. Since the replacement isn't yet ready, it has not been removed.
Sorry to be so non-committal, but it seems like XDS is a better long term LB solution, and we don't want to support two competing implementations. On Saturday, February 23, 2019 at 12:48:43 AM UTC-8, [email protected] wrote: > > And what about SRV records lookup: now I have to set this flag: > > io.grpc.internal.DnsNameResolverProvider.enable_grpclb >> > > to true, and there was a commit some time ago which enabled it by default: > https://github.com/grpc/grpc-java/commit/c729a0f76b244da9f4aebc40896b2fb891d1b5c4 > > and now it has been reverted: https://github.com/grpc/grpc-java/pull/5232 > - how it is eventually going to be? > > > W dniu piątek, 22 lutego 2019 21:16:54 UTC+1 użytkownik Penn (Dapeng) > Zhang napisał: >> >> Neither grpclb nor xds will be enabled by default, grpclb need be >> explicitly enabled by a service config or a ManagedChannelBuilder option, >> and xds need be explicitly enabled by a service config. Grpclb will >> eventually be replaced by xds based solution in the future, but the >> grpc-grpclb <https://search.maven.org/search?q=a:grpc-grpclb> maven >> artifact will stay and work for a long time (for as many new releases as >> possible). When grpclb is not available for a new grpc release, your client >> can still automatically switch to a fallback loadbalancer (pick_first). >> >> On Friday, February 22, 2019 at 8:52:16 AM UTC-8, [email protected] >> wrote: >>> >>> What is the status of GRPCLB - are there any plans to enable it by >>> default and finish the experimental stage (we want to start using it in >>> production), or opposite, you plan to abandon it? I am confused, because >>> I've read this PR: https://github.com/grpc/grpc-java/pull/5232: >>> >>> SRV has not yet been enabled in a release. >>>> >>>> *Since work is rapidlyunderway to replace GRPC-LB with a service >>>> config+XDS-based solution,there's now thoughts that we won't ever enable >>>> grpclb by default* (but >>>> may allow it to be automatically enabled when using GoogleDefaultChannel >>>> or similar). Since things are being worked out, disable it. >>> >>> >>> It will be really helpful to us to know, what is the plan for it :) >>> >> -- 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/e49e764a-9e2f-41b6-9b89-e69f1332bf36%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
