简体繁体 English

从非集群配置的石英调度程序实例将作业调度到集群的石英1.8.6

[英]scheduling jobs to clustered quartz1.8.6 from non-cluster configured quartz scheduler instance

原文 2017-01-31 12:35:22 5 1 jdbc/ locking/ mixing/ contention/ quartz

I'm using quartz 1.8.6 in clustered mode with 4 instances. 我在具有4个实例的群集模式下使用石英1.8.6。 Now, I observed high contention on table QRTZ_LOCKS. 现在，我发现在表QRTZ_LOCKS上的争用很高。 My application also provide webservices for online clients. 我的应用程序还为在线客户提供Web服务。 This webservices also do scheduling of new jobs. 该Web服务还可以安排新作业。 Now, I see timeout exceptions on those webservices, because when they want to schedule new job they wait too loooong to obtain lock on QRTZ_LOCKS table. 现在，我看到了这些Web服务的超时异常，因为当他们要安排新作业时，他们太懒得等待以获取对QRTZ_LOCKS表的锁定。 It's important for me to establish 100% reliable operation for webservices (more important than quartz jobs operations). 对我来说，为Web服务建立100％可靠的运行非常重要（比石英作业更重要）。 Is it possible to start quartz job runner on 1 instance only and other 3 instances configure with org.quartz.jobStore.isClustered=false to allow them perform scheduling WITHOUT getting lock on QRTZ_LOCKS? 是否可以仅在1个实例上启动石英作业运行器，而其他3个实例使用org.quartz.jobStore.isClustered = false配置，以允许他们执行调度而无需锁定QRTZ_LOCKS？

update: Actually, if I plan to run only one instance with job runner and all others just allowed to add new jobs this won't be a cluster anymore. 更新：实际上，如果我计划仅运行一个带有作业运行程序的实例，而其他所有仅允许添加新作业的实例，则该实例将不再是集群。 So, actual question would be: is it possible to configure org.quartz.jobStore.isClustered=false to all 4 instances, make only 1 instance run jobs, but allow all 4 to schedule new jobs to same jdbc storage? 因此，实际的问题是：是否可以为所有4个实例配置org.quartz.jobStore.isClustered = false，仅使1个实例运行作业，但允许所有4个将新作业调度到相同的jdbc存储中？

1 个解决方案

Try to turn batch mode on, and set maximum batch count to the amount of threads, available for quartz scheduler. 尝试打开批处理模式，并将最大批处理计数设置为石英调度程序可用的线程数量。

http://www.ebaytechblog.com/2016/01/14/performance-tuning-on-quartz-scheduler/ http://www.ebaytechblog.com/2016/01/14/performance-tuning-on-quartz-scheduler/