And I found if I set org.quartz.jobStore.isClustered to false. volatile feature seems to be OK. If I set this params to true, even when there's only one scheduler node in cluster, volatile cannot work.
Question is when quartz clear the volatile jobs/triggers, at shutting down, or at starting up? And what's the proper behavior in a cluster?
Suggest that,
1) Clear volatile jobs/triggers in starting-up (after experiment, found non-clustered scheduler just works like that)
2) If Whole cluster restarts, clear the volatile ones by first node who owns the lock (seems not implemented)
Hi experts,
I use mysql backend as jobstore on quartz-1.8.4. In setting a job, I set both endless secondly SimpleTrigger and JobDetails to setVolatility(true). First I scheduled the job through code, and run. Then I remove the schedule job code, keep a simple scheduler.start() call and restart the JVM, I found the job is still scheduled and running every second. Is this a expected behavior of volatile job/trigger?
Here's my scheduler config:
######################
#============================================================================
# Configure Main Scheduler Properties
#============================================================================
org.quartz.scheduler.instanceName = MY_SCHEDULER
org.quartz.scheduler.instanceId = AUTO