What will be the impact on Dubbo service publication / subscription after ZooKeeper registry restart

In this issue, the editor will bring you about the impact of ZooKeeper registry restart on Dubbo service publication / subscription. The article is rich in content and analyzes and describes for you from a professional point of view. I hope you can get something after reading this article.

Situation: ZooKeeper cluster deletes all data. After restarting ZooKeeper cluster, im-service has no providers.

After restarting im-service, all dubbo interfaces of im-service do not have consumers.

After restarting im-web, everything ok.

Conclusion: problem: if the dubbo service is running properly, but the ZooKeeper cluster is down and all data is lost. Do I need to restart the dubbo service after the ZooKeeper cluster is restarted? Answer: yes. -problem: if the dubbo service is running normally, but the ZooKeeper cluster is down and no data is lost (zk data is persisted). Do I need to restart the dubbo service after the ZooKeeper cluster is restarted? Answer: no need. Software environment:

ZooKeeper 3.4.11

Dubbo 2.5.3

Verify:

1. In the docker container, start the ZooKeeper cluster

2. Start the gwy-res-web project locally.

This project is both provider and consumer: