Is registration center can use now ? If registration center is ready, registration center is better.
CalvinKirs <[email protected]> 于2020年10月27日周二 上午9:57写道： > registration center +1 > Hello, I think the registration center is relatively more flexible, and it > can also help us manage the online and offline of alerts. If in the future, > alert-server supports multiple deployments, the role of zk is more obvious. > > > Best wishes！ > CalvinKirs > > > On 10/27/2020 09:48，zhuangchong6<[email protected]> wrote： > https://github.com/apache/incubator-dolphinscheduler/issues/3997 > > > > Describe the question > In the case of the SqlTask task, the task needs to send messages > synchronously, and the final running status of this task depends on whether > the message is sent successfully. Therefore, the alarm api needs to send > messages synchronously. > Have a problem at this time? There are two ways to get the alert api for > the SqlTask task: put the alertserver address into the configuration file > of the worker or master; put the alertserver address into the zk > registration center; it is recommended to use the first one, the first > version is simple to implement, and there will be alertserver load later > Related issues will also consider registry issues > Do you have any suggestions? > > Which version of DolphinScheduler: > -[alert_plugin_design] > > 描述问题 > 在SqlTask任务情况下，任务需要同步发送消息，此任务的最终运行状态取决于消息是否发送成功。 因此，告警api需要同步发送消息。 > 此时有个问题？SqlTask > 任务如何获取告警api，下面有两种方式：alertserver地址放入worker或master的配置文件；alertserver地址放入zk注册中心; > 推荐使用第一种，第一版先简单实现，后期会有alertserver负载相关问题也会考虑注册中心问题。 > 大家有什么建议么？ > > 哪个版本的DolphinScheduler： > -[alert_plugin_design]
