Terracotta Discussion Forums
Search
Recent Topics
Member Listing
Back to home page
Register
/
Login
quartz 2.1 clustering job scheduling fires the same trigger on different machines intermittently
Forum Index
->
Quartz
Author
Message
08/06/2012 05:09:08
Subject:
quartz 2.1 clustering job scheduling fires the same trigger on different machines intermittently
gsan12
journeyman
Joined: 08/06/2012 04:53:56
Messages: 14
Offline
Hello,
I need a help for the quartz-2.1.0 clustering problem.
I have setup the clustering with 2 machines with single mysql as the JobStore.
#============================================================================
# Configure Main Scheduler Properties
#============================================================================
org.quartz.scheduler.instanceName = MyClusteredScheduler
org.quartz.scheduler.instanceId = AUTO
#============================================================================
# Configure ThreadPool
#============================================================================
org.quartz.threadPool.class = org.quartz.simpl.SimpleThreadPool
org.quartz.threadPool.threadCount = 25
org.quartz.threadPool.threadPriority = 5
#============================================================================
# Configure JobStore
#============================================================================
org.quartz.jobStore.misfireThreshold = 60000
org.quartz.jobStore.class = org.quartz.impl.jdbcjobstore.JobStoreTX
org.quartz.jobStore.driverDelegateClass = org.quartz.impl.jdbcjobstore.StdJDBCDelegate
org.quartz.jobStore.useProperties = false
org.quartz.jobStore.dataSource = myDS
org.quartz.jobStore.tablePrefix = QRTZ_
org.quartz.jobStore.isClustered = true
org.quartz.jobStore.clusterCheckinInterval = 20000
#============================================================================
# Configure Datasources
#============================================================================
org.quartz.dataSource.myDS.driver = oracle.jdbc.driver.OracleDriver
org.quartz.dataSource.myDS.URL = jdbc:mysql://mydb.com:3306/quartz
org.quartz.dataSource.myDS.user = quartz
org.quartz.dataSource.myDS.password = quartz
org.quartz.dataSource.myDS.maxConnections = 5
org.quartz.dataSource.myDS.validationQuery=select 1
I scheduled a job, but it intermittently fires the same triggers in the both machines(sometimes).
ex: A job having a single trigger which will fire after every 1min.
most of the time it will be fired in only one of the machines.
but intermittently it fires in both the machines.
time is synced to the ntp server in the network.
Am I doing anything wrong ?
Hopefully someone will help me out. L
Thanks & Regards,
Santhosh
08/06/2012 13:13:55
Subject:
Re:quartz 2.1.0 clustering job scheduling fires the same trigger on different machines
jhouse
seraphim
Joined: 11/06/2009 15:29:56
Messages: 1654
Online
Are you using innodb tables?
08/06/2012 13:14:51
Subject:
Re:quartz 2.1 clustering job scheduling fires the same trigger on different machines intermittently
jhouse
seraphim
Joined: 11/06/2009 15:29:56
Messages: 1654
Online
also, any reason you can't upgrade to 2.1.5 ?
08/06/2012 22:14:02
Subject:
Re:quartz 2.1 clustering job scheduling fires the same trigger on different machines intermittently
gsan12
journeyman
Joined: 08/06/2012 04:53:56
Messages: 14
Offline
yes, we are using innodb. Is there any bug ?
we haven't thought of upgrade yet.
Is it resolved in quartz-2.1.5?
08/07/2012 08:05:50
Subject:
Re:quartz 2.1 clustering job scheduling fires the same trigger on different machines intermittently
jhouse
seraphim
Joined: 11/06/2009 15:29:56
Messages: 1654
Online
IIRC, there was some similar bug in 2.1.0.
08/08/2012 01:51:55
Subject:
Re:quartz 2.1 clustering job scheduling fires the same trigger on different machines intermittently
gsan12
journeyman
Joined: 08/06/2012 04:53:56
Messages: 14
Offline
Could you please provide the bug details (JIRA) ticket or something.?
Actually,
After changing the
org.quartz.jobStore.acquireTriggersWithinLock
to
true
.
This issue never happened again.
Do u think org.quartz.jobStore.acquireTriggersWithinLock=false with loadbalance setup causes this issue?
Do u see any problem with this configuration?
Thanks & Regards,
Santhosh
Forum Index
->
Quartz
Go to:
Select a forum
BigMemory
Ehcache
General
Quartz
BigMemory + Hadoop
Terracotta for Web Sessions
Terracotta Platform
Terracotta Licensing
Terracotta 中文社区
Terracotta for Spring
Powered by
JForum 2.1.7
©
JForum Team