ruanwenjun commented on issue #10874: URL: https://github.com/apache/dolphinscheduler/issues/10874#issuecomment-1192672340
> > > Is it is a must to implement `distributed lock` in dolphinscheduler? > > > As far as I know, `distributed lock` in current version, is used for making sure only one master handling requests or failover event. > > > Is it ok If we just put above logics in Leader Master? > > > > > > This is not a good idea, you need to import the `leader` role in other registry plugin. > > In fact not, with raft introduced, we will introduce leader and followers in this system, no need to rely on other registry plugins. > > method details pros cons > raft with distributed lock multiple master handling tasks no pressure on single master extra dependency/implementation of distributed lock > raft without distributed lock only the raft leader handling tasks simple, popular way(like Apache Ozone, Alibaba RemoteShuffuleService) pressure on single master > I feel both are OK We need to reach a consensus that we import raft just as a new registry plugin, this will not affect our existing plugin. -- 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]
