-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
当设置isMonitorExecution=true后,等待积压任务应该能够设置timeout #49
Comments
目前quartz设定的是用1个线程池 |
我看代码misfire应该是分片维度的,不是调度批次维度的,如果2台机器【1,2】,【3,4】,第一次调度后【1,2】数据少执行较快,【3,4】数据较多执行较慢,达到第二次调度时间时可能上次【3,4】还没执行完,这时候第二次调度的时候【1,2】会继续运行,但是【3,4】设置了misfire |
是的,是担心一个分片执行不完整个下次作业都不能执行。如果想讨论misfire的事情,可以另开启一个issue |
while (executionService.hasRunningItems()) { |
Expired |
当设置isMonitorExecution=true后:
while (executionService.hasRunningItems()) {
log.debug("Elastic job: sleep short time until other job completed.");
BlockUtils.waitingShortTime();
}
当任务由于某些原因阻塞的话,后面的任务仍然会依次启动并进入等待队列,最坏的情况可能出现stackOverFlowException。
应当提供可选配置等待timeout,达到后退出while循环并报警。
The text was updated successfully, but these errors were encountered: