KenyeeCheung

the parameters of previous cached is (1, 2)

Redis.on("reconnect") or redis.on("close") is not enough, and I see that node of cluster has connecter object, and it knows if the node is connecting.

1. nacos 的 serviceName 一般是 providers:interface:version:group 2. consumer 注册的 serviceName 直接就是 interface，应该也是 consumers:interface:version:group 这种格式才对的 3. 因为上面两个原因，在 [registry-nacos.ts](https://github.com/apache/dubbo-js/blob/28e499b0b5e9e862945ad3d7461cba34e233f82f/packages/dubbo-registry/src/registry-nacos.ts#L95)中，直接用 interface 去搜索，搜索到的都是本地的，所以没办法使用第三方提供的 nacos 服务 参考 java 的实现 https://github.com/apache/dubbo/blob/master/dubbo-registry/dubbo-registry-nacos/src/main/java/org/apache/dubbo/registry/nacos/NacosServiceName.java#L206

看了 duubo.ts 的代码发现 [proxyService](https://github.com/apache/dubbo-js/blob/28e499b0b5e9e862945ad3d7461cba34e233f82f/packages/dubbo-consumer/src/dubbo.ts#L209) 方法只是单纯的返回自己，与 DubboDirectlyInvoker 的实例的 proxyService 表现不一样，希望有相同的表现，或者可以将 [consumeService](https://github.com/apache/dubbo-js/blob/28e499b0b5e9e862945ad3d7461cba34e233f82f/packages/dubbo-consumer/src/dubbo.ts#L113) 改为 public 的方法

[BUG] The problem of health check in gRPC service-to-service invocation

4

#### What happened: I have two Kratos services that call each other through gRPC. My gRPC connection is established via a domain name, and there are multiple IPs behind this...