[Building Sakai] Question about org.quartz.jobStore.isClustered

[Matthew Jones]

I don't think you actually can set this (Sakai) property and have it do
anything, you actually have to set that it on quartz.properties by
rebuilding jobscheduler or have this patch from Sakai 10 (
https://jira.sakaiproject.org/browse/SAK-20885) so that you can change this
file without rebuilding jobscheduler.

I haven't actually tested it, but if you have certain jobs in certain
environments that start up on 2 different nodes in a cluster can cause
problems with the database and processing. It's difficult to test because
we have no QA instances clustered, and many places that do run clustered
actually disable quartz with this patch in 2.9.x (
https://jira.sakaiproject.org/browse/SAK-13776) or something similar so
that quartz is only running on one node in a cluster anyway. (Eliminating
any possibility of problems) One such job that I know has been an issue in
the past is the synoptic message counts job that causes Oracle constraint
violations.

It *seems* like it's likely useful, but also seems like it would take a
good amount of time to test to say for sure what it really does, as I never
found any information about it specifically.



On Wed, Feb 19, 2014 at 12:34 PM, Joshua Swink <joshua.swink at gmail.com>wrote:

> The README in jobscheduler advises setting org.quartz.jobStore.isClustered
> to true when using it in a cluster. Is this actually useful? I've been
> running Sakai with scheduled jobs for quite a while without setting this.
>
> Josh
>
> _______________________________________________
> 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/20140219/e4b14dac/attachment.html