Is it more appropriate to put it in common module ?
reason :
1，Now server module email alert, but it may not be ruled out that in the
future, for example, the api server module will also use the alert.
2，Another problem is that it is better to store the warning information.
That is, it is stored in the database before sending, and then the database is
updated after sending.
Can keep some warning information. Of course, except the case where the
SQL task sends email directly
―――――――――――――
DolphinScheduler(Incubator) PPMC
Zhanwei Qiao 乔占卫
[email protected]
发件人： Xiaochun Liu<mailto:[email protected]>
发送时间： 2019-12-11 17:02
收件人： dev<mailto:[email protected]>
主题： Re: Aproposal for DolphinScheduler Simplified Deployment
+ 1
Best Regards
---------------
DolphinScheduler(Incubator) Committer
Xiaochun Liu 刘小春
[email protected]
---------------
> 在 2019年12月11日，下午5:00，guo jiwei <[email protected]> 写道：
>
>
> General Implementation:
> 1. Combine alert module into server module. Create a new package for
> alert function.
> 2. MasterServer is responsible for alert. When starts MasterServer,
> startup alert server.
> 3. We can use zk lock to round-robin doing the alert around the
> MasterServer. or just leader do(for it uses little resource)
