Rubik-W opened a new issue #2351: [Feature] api server, timing management interface depends on Quartz URL: https://github.com/apache/incubator-dolphinscheduler/issues/2351 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.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
