[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: |
|
||||||||
| Issue Links: |
|
||||||||
| 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:
|
| 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. |