hddong commented on code in PR #2767:
URL: https://github.com/apache/incubator-kyuubi/pull/2767#discussion_r902415773


##########
externals/kyuubi-spark-sql-engine/src/main/resources/META-INF/services/io.grpc.LoadBalancerProvider:
##########
@@ -0,0 +1,3 @@
+io.grpc.internal.PickFirstLoadBalancerProvider
+io.grpc.util.SecretRoundRobinLoadBalancerProvider$Provider
+io.grpc.grpclb.GrpclbLoadBalancerProvider

Review Comment:
   > What doesn't relocate them?
   
   Had do this, and got
   ```scala
   Caused by: java.lang.IllegalArgumentException: cannot find a NameResolver 
for ip:///100.71.36.42:2389
           at 
org.apache.kyuubi.shade.io.grpc.internal.ManagedChannelImpl.getNameResolver(ManagedChannelImpl.java:776)
           at 
org.apache.kyuubi.shade.io.grpc.internal.ManagedChannelImpl.getNameResolver(ManagedChannelImpl.java:785)
           at 
org.apache.kyuubi.shade.io.grpc.internal.ManagedChannelImpl.<init>(ManagedChannelImpl.java:665)
           at 
org.apache.kyuubi.shade.io.grpc.internal.ManagedChannelImplBuilder.build(ManagedChannelImplBuilder.java:630)
           at 
org.apache.kyuubi.shade.io.grpc.internal.AbstractManagedChannelImplBuilder.build(AbstractManagedChannelImplBuilder.java:297)
           at 
org.apache.kyuubi.shade.io.vertx.grpc.VertxChannelBuilder.build(VertxChannelBuilder.java:302)
           at 
io.etcd.jetcd.impl.ClientConnectionManager.getChannel(ClientConnectionManager.java:89)
   ```
   Although we provide `IPResolverProvider` in `nameresolverprovider`, 
`NameResolver` can not load `IPResolverProvider`, we can relocate them after a 
solution is found.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to