leo-lao commented on issue #10874:
URL:
https://github.com/apache/dolphinscheduler/issues/10874#issuecomment-1192603254
> > 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,
no need to rely on other registry plugins.
[](url)
<table>
<tr>
<td>method</td>
<td>details</td>
<td>pros</td>
<td>cons</td>
<td>
<tr>
<td>raft with distributed lock</td>
<td>multiple master handling tasks</td>
<td>no pressure on single master</td>
<td>extra dependency/implementation of distributed lock</td>
<tr>
<td>raft without distributed lock</td>
<td>only the raft leader handling tasks</td>
<td>simple, popular way(like Apache Ozone, Alibaba
RemoteShuffuleService)</td>
<td>pressure on single master</td>
</table>
I feel both are OK
--
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]
