OK, I understand. Api server and master server share a quartz instance, share a quartz config file. So, no problem keeping the current configuration.
原始邮件 发件人: guo jiwei<[email protected]> 收件人: dev<[email protected]> 发送时间: 2020年4月3日(周五) 10:44 主题: Re: Api server, timing management interface depends on Quartz This is a default value, for we want to use in server module only. But as development goes, and api module uses the same config as server. so causes the issue. We will refactor quartz in the future. but in current version, you can set it as below in api module。 org.quartz.threadPool.threadCount = 1 On Fri, Apr 3, 2020 at 12:20 AM lidong dai <[email protected]> wrote: > this issue: > https://github.com/apache/incubator-dolphinscheduler/issues/2356 > forward > to mail list, haha > > > Best Regards > --------------- > DolphinScheduler(Incubator) PPMC > Lidong Dai 代立冬 > [email protected] > --------------- > > > whm_777 <[email protected]> 于2020年4月2日周四 下午4:32写道： > > > hi, everyone ! > > > > > > Now, In the api server, on-line and off-line tasks depend on quartz > > scheduler. > > QuartzExecutors.getInstance().addJob(ProcessScheduleJob.class, jobName, > > jobGroupName, startDate, endDate, schedule.getCrontab(), dataMap); > > if(!QuartzExecutors.getInstance().deleteJob(jobName, jobGroupName)){ > > logger.warn("set offline > > failure:projectId:{},scheduleId:{}",projectId,scheduleId); throw new > > RuntimeException(String.format("set offline failure")); } > > QuartzExecutors.getInstance(): > > SchedulerFactory schedulerFactory = new > > StdSchedulerFactory(Constants.QUARTZ_PROPERTIES_PATH); scheduler = > > schedulerFactory.getScheduler(); > > org.quartz.threadPool.threadCount = 25 > > 25 worker threads are initialized by default. > > These threads will never be used. > > > > > > I didn't think about how to solve it, welcome to discuss. >
