Hello everyone . Simplify deployment is very nice to users. Currently, we have discussed combining or decreasing configuration files . How about deleting alert module ? We can move alert module into server module . MasterServer can take the responsibility for the task alert .
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) If this proposal is taken into consideration , users do not to deploy alert module anymore . On Tue, Dec 10, 2019 at 2:24 PM qiao zhanwei <[email protected]> wrote: > > Hello All , > > Now DolphinScheduler has so many Configuration files > > for example : > > dolphinscheduler-alert : > alert.properties > > dolphinscheduler-api : > application-api.properties > application-combined.properties > > > dolphinscheduler-common : > hadoop.properties > common.properties > quartz.properties > zookeeper.properties > > dolphinscheduler-dao : > application-dao.properties > > dolphinscheduler-server : > application-master.properties > application-master.properties > master.properties > worker.properties > > .dolphinscheduler_env.sh > > Can we simplify deployment ? > > Main point : > > 1 configuration file simplification and merged configuration file > 2 master server remove port > 3 support offline installation，remove kazoo dependencies in install and > monitor > 4 instll.sh script simplification > > > ————————————— > DolphinScheduler(Incubator) PPMC > Zhanwei Qiao 乔占卫 > > [email protected] >
