[Building Sakai] Quartz job scheduler & multiple app servers

[David Horwitz]

Hi Paul,

The job scheduler is cluster aware (with some caveats) so there should 
be no need to disable it on the second node.

The behaviour:

1) A single trigger will only start 1 job on the cluster
2) If a job is running and its schedule comes up again (e.g. cron 
trigger for every 5 minutes and the job runs > 5min):
     a) If the job implements Job a new job is started
     b) if the job implements StatefulJob no new job will be started

I don't think though the behaviour of 2 changes with clustering ....


D

On 03/09/2012 11:22 PM, Paul Dagnall wrote:
> Hi
> We're about to put a second application server into production. We're 
> previously been running with just one. I was wondering how to handle 
> the Quartz Job Scheduler. Will there be conditions where the two app 
> servers try to run the same scheduled job at the same time, or is it 
> able to lock after one gets there first?
>
> I didn't see a property to disable the job scheduler. Other than just 
> not deploying the tool on one server instance, I'm not sure how to 
> otherwise control it. What do you recommend?
>
> Thank you!
>
> Paul Dagnall
> Application Developer & Administrator
> University of Dayton
>
>
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20120310/1130f3e6/attachment.html