You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@dolphinscheduler.apache.org by GitBox <gi...@apache.org> on 2020/04/01 06:41:21 UTC
[GitHub] [incubator-dolphinscheduler] Rubik-W opened a new issue #2351:
[Feature] api server, timing management interface depends on Quartz
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:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [incubator-dolphinscheduler] dailidong commented on issue #2351:
[Feature] api server, timing management interface depends on Quartz
Posted by GitBox <gi...@apache.org>.
dailidong commented on issue #2351: [Feature] api server, timing management interface depends on Quartz
URL: https://github.com/apache/incubator-dolphinscheduler/issues/2351#issuecomment-607945492
the deep discussion moved to the mail list : https://lists.apache.org/thread.html/r692bad0ac8b9626388504300e635b935b93518e6a06311c4a5f16560%40%3Cdev.dolphinscheduler.apache.org%3E
----------------------------------------------------------------
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:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [incubator-dolphinscheduler] Technoboy- commented on issue #2351:
[Feature] api server, timing management interface depends on Quartz
Posted by GitBox <gi...@apache.org>.
Technoboy- commented on issue #2351: [Feature] api server, timing management interface depends on Quartz
URL: https://github.com/apache/incubator-dolphinscheduler/issues/2351#issuecomment-608254617
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
----------------------------------------------------------------
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:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [incubator-dolphinscheduler] dailidong commented on issue #2351:
[Feature] api server, timing management interface depends on Quartz
Posted by GitBox <gi...@apache.org>.
dailidong commented on issue #2351: [Feature] api server, timing management interface depends on Quartz
URL: https://github.com/apache/incubator-dolphinscheduler/issues/2351#issuecomment-607290493
Do you think the proper value of `org.quartz.threadPool.threadCount` is ?
----------------------------------------------------------------
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:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [incubator-dolphinscheduler] dailidong closed issue #2351:
[Question] api server, timing management interface depends on Quartz
Posted by GitBox <gi...@apache.org>.
dailidong closed issue #2351: [Question] api server, timing management interface depends on Quartz
URL: https://github.com/apache/incubator-dolphinscheduler/issues/2351
----------------------------------------------------------------
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:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [incubator-dolphinscheduler] Rubik-W commented on issue #2351:
[Feature] api server, timing management interface depends on Quartz
Posted by GitBox <gi...@apache.org>.
Rubik-W commented on issue #2351: [Feature] api server, timing management interface depends on Quartz
URL: https://github.com/apache/incubator-dolphinscheduler/issues/2351#issuecomment-607602940
This is not a problem with threadCount parameter.
The api server should not initialize the quartz thread pool, the master server uses these threads. When the api server is running and do on-line task timing, you can look at the thread pool (jstack).
----------------------------------------------------------------
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:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [incubator-dolphinscheduler] Rubik-W commented on issue #2351:
[Feature] api server, timing management interface depends on Quartz
Posted by GitBox <gi...@apache.org>.
Rubik-W commented on issue #2351: [Feature] api server, timing management interface depends on Quartz
URL: https://github.com/apache/incubator-dolphinscheduler/issues/2351#issuecomment-608256375
OK, I understand.
Api server and master server share a quartz instance, share a quartz config file.
So, no problem keeping the current configuration.
----------------------------------------------------------------
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:
users@infra.apache.org
With regards,
Apache Git Services