github-actions[bot] commented on issue #10874:
URL: 
https://github.com/apache/dolphinscheduler/issues/10874#issuecomment-1179684176

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and 
found no similar feature requirement.
   
   
   ### Description
   
   ## The current role of zookeeper
   1. Store service-related information of master and worker, host IP, port, 
cpu load, etc.
   2. Master and worker health check
   3. master failover
   4. Distributed lock
   ## Problems caused by zookeeper
   1. Increase the complexity of system deployment and operation and 
maintenance. While deploying the DS cluster, a zookeeper cluster should also be 
deployed. It is also necessary to monitor the operation and maintenance of the 
DS cluster and the zookeeper cluster at the same time
   1. Increase the chance of error. The network between the DS cluster and the 
zookeeper cluster is fluttering, and errors may occur.
   
   ## remove zookeeper's point
   1. The deployment architecture is simpler
   2. Lower maintenance cost
   3. No more DS errors due to zookeeper cluster errors
   
   ## remove zookeeper scheme
   <img width="700" alt="image" 
src="https://user-images.githubusercontent.com/13765310/178137541-39521953-39f9-40ff-9008-df983e66d1b8.png";>
   
   1. Refer to Kafka's KRaft solution to achieve leader election and data 
synchronization between masters
   2. The worker server registers with the leader master and maintains a 
heartbeat with the master
   3. Api server obtains cluster information from leader master
   
   
   
   ### Use case
   
   _No response_
   
   ### Related issues
   
   #6680
   
   ### Are you willing to submit a PR?
   
   - [X] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)


-- 
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]

Reply via email to