sorry for wrong issue id, this issue id, this is right issue url: https://github.com/apache/incubator-dolphinscheduler/issues/2351
Best Regards --------------- DolphinScheduler(Incubator) PPMC Lidong Dai 代立冬 [email protected] --------------- lidong dai <[email protected]> 于2020年4月3日周五 上午12:19写道： > 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. > >
