@flystar32 1. dubbo支持多注册，多消费 可以将你们的Provider为每个注册中心都注册一份数据，消费方消费多个注册中心服务，目前dubbo是按照配置注册中心的循序进行消费，比如是配置了redis, zk注册中心，优先消费redis服务，如果redis没有服务会自动去消费zk服务
2. 这个和注册中心实现没有关系, 有2中方法可以支持你的需求： a. org.apache.dubbo.config.ReferenceConfig#createProxy AvailableCluster 默认是根据配置顺序消费注册中心数据，可以实现新的Cluster决定消费策略 b. 你可以实现一个路由Router，多个注册中心在运行时动态决定消费哪个注册中心服务 Google translation： Dubbo supports multiple registrations, more consumption You can register your Provider for each registration center, and the consumer consumes multiple registration center services. Currently, dubbo is consumed according to the configuration registration center. For example, redis, zk registration center, priority consumption redis Service, if redis no service will automatically consume zk service This has nothing to do with the registry implementation. There are 2 ways to support your needs: a. org.apache.dubbo.config.ReferenceConfig#createProxy AvailableCluster defaults to consuming registry data sequentially according to configuration b. You can implement a routing router, and multiple registries dynamically determine which registrar service to consume at runtime. [ Full content available at: https://github.com/apache/incubator-dubbo/issues/3084 ] This message was relayed via gitbox.apache.org for [email protected]
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
