Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

dashboard quartz job runs inconsistent with quartz trigger definition

Description

The repetitive maintenance Dashboard jobs (calendar repeating event handling, expire and purge old records, and check item availability) are running inconsistent with quartz job trigger definitions.

Based on the records in qrtz_fired_triggers, all those jobs have been triggers successfully based on the trigger definition. However, we only observed the dashboard job execution randomly among those job firing times.

Activity

Matthew Jones April 24, 2016 at 9:54 AM

I feel like leaving this critical would be fine but this might just be documentation and additional testing in a cluster to fix (not many code changes). There are various issues in the past with jobs running in a clustered environment that are hard to test on dev, and that's mostly what this ticket and the comments refer to.

I don't believe this method of running dashboard was ever tested very well and not deployed much.

I believe this might be fixed in two ways either:

  • Disabling quartz on every server except a single node (via with startScheduler@org.sakaiproject.api.app.scheduler.SchedulerManager=false)

  • Putting a custom quartz.properties in sakai.home () that has the setting for org.quartz.jobStore.isClustered = true

Jeff Pasch April 23, 2016 at 10:31 PM

Hi and . Can you advise on what the priority on this one should be? Jobs "running inconsistent with quartz job trigger definitions" seems serious (especially the "check item availability")

Details

Assignee

Reporter

Labels

Components

Affects versions

Priority

Created January 29, 2014 at 12:52 PM
Updated August 1, 2016 at 11:09 AM