SbloodyS commented on code in PR #17092: URL: https://github.com/apache/dolphinscheduler/pull/17092#discussion_r2018317385
########## docs/docs/en/architecture/design.md: ########## @@ -59,21 +59,25 @@ - **RetryReportTaskStatusThread** is mainly responsible for regularly polling to report the task status to the Master until the Master replies to the status ack to avoid the loss of the task status; -* **ZooKeeper** +- **ZooKeeper** - ZooKeeper service, MasterServer and WorkerServer nodes in the system all use ZooKeeper for cluster management and fault tolerance. In addition, the system implements event monitoring and distributed locks based on ZooKeeper. + ZooKeeper service, MasterServer and WorkerServer nodes in the system all use ZooKeeper for cluster management and fault tolerance. With evolving needs and modern deployment environments, DolphinScheduler now supports event monitoring and distributed locks not only based on ZooKeeper, but also on **JDBC** and **Etcd** implementations. + + - **JDBC** provides a lightweight solution for lock and event management through relational databases, making it ideal for simpler deployments or systems that already rely heavily on SQL databases. + + - **Etcd** enables distributed coordination using a high-performance key-value store, suitable for modern cloud-native environments. Review Comment: This has nothing to do with `Jdbc/Etcd implementation for event monitoring and distributed lock`. Just a simple description of `JDBC` and `Etcd`. -- 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]
