Dubbo Study Notes

First, zookeeper play a role in the Dubbo

Process:
1. The service provider writes the URL to the/dubbo/com.foo.barservice/providers directory when it starts
2. Service consumers at startup subscribe to the URL under the/dubbo/com.foo.barservice/providers directory to write their own URL to the/dubbo/com.foo.barservice/consumers directory
3. When monitoring Center starts, subscribe to all provider and consumer URLs in the/dubbo/com.foo.barservice directory

The following features are supported:

1. The registry can automatically delete provider information when there is an abnormal outage such as a power outage.

2. When the registry restarts, the registration data can be automatically restored, as well as the subscription request.

3. When the session expires, the registration data can be automatically restored, as well as the subscription request.

4. When setting <dubbo:registry check= "false"/>, log failed registration and subscription request, background timed retry.

5. You can set/> login information via <dubbo:registry username= "admin" password= "1234" zookeeper.

6. The root node of zookeeper can be set by <dubbo:registry group= "Dubbo"/>, and no root tree will be used.

7. Support for the * number wildcard <dubbo:reference group= "*" version= "*"/>, all groups and providers of all versions of the service can be subscribed to.

Note that Ali internal does not use zookeeper as a registry, but the use of their own implementation of the database-based registry, that is: Zookeeper registry does not have long-running reliability within Ali, this zookeeper bridge implementation is only available for the open source version, Its reliability depends on the reliability of the zookeeper itself. Second, zookeeper view transaction log Java-classpath.: Slf4j-api-1.6.1.jar:zookeeper-3.4.5.jar Org.apache.zookeeper.server.logformatter/export1/zookeeper/logs/version-2/log.1000003d2

Dubbo Study Notes