[MGNLSCH-18] Support non-concurrent execution of jobs Created: 14/Dec/10  Updated: 10/Mar/11  Resolved: 18/Jan/11

Status: Closed
Project: Scheduler
Component/s: None
Affects Version/s: 1.4
Fix Version/s: 1.4.1

Type: New Feature Priority: Neutral
Reporter: Magnolia International Assignee: Philipp Bärfuss
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File MGNLSCH-18.patch    
Issue Links:
dependency
is depended upon by MGNLFORUM-130 Synchronizer module, providing bi-dir... Closed
Template:
Patch included:
Yes
Acceptance criteria:
Empty
Date of First Response:

 Description   

When a job takes a long time to execute but is scheduled often, it might be desirable to avoid concurrent executions of the job.

It seems like implementing the StatefulJob interface could be enough to achieve this. Here's a simple patch that allows Magnolia jobs to be configured as non-concurrent.

To review: implications of this change:

  1. should we make this the default behavior ? (attached patch keeps the concurrent flag to true, i.e. the current default behavior)
  2. do we use a store for our jobs, should we, especially if we're starting to have long-running jobs ?


 Comments   
Comment by Magnolia International [ 14/Dec/10 ]

updated patch without unnecessary system.out's.

Comment by Magnolia International [ 22/Dec/10 ]

Patch applied. Can we double-check implications, if we should change the default behavior and what to do with long-running jobs ?

Comment by Philipp Bärfuss [ 18/Jan/11 ]

Marking it as resolved to make it ready for the review.

Generated at Mon Feb 12 10:45:05 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.