[
http://jira.magnolia-cms.com/browse/MGNLSCH-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grégory Joseph updated MGNLSCH-18:
----------------------------------
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:
# should we make this the default behavior ? (attached patch keeps the
concurrent flag to true, i.e. the current default behavior)
# do we use a store for our jobs, should we, especially if we're starting to
have long-running jobs ?
was:
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:
# should we make this the default behavior ? (attached patch keeps the
concurrent flag to true, i.e. the current default behavior)
# do we use a store for our jobs, should we, especially if we're starting to
have long-runing jobs ?
> Support non-concurrent execution of jobs
> ----------------------------------------
>
> Key: MGNLSCH-18
> URL: http://jira.magnolia-cms.com/browse/MGNLSCH-18
> Project: Magnolia Scheduler Module
> Issue Type: New Feature
> Affects Versions: 1.4
> Reporter: Grégory Joseph
> Assignee: Philipp Bärfuss
> Fix For: 1.4.1
>
> Attachments: MGNLSCH-18.patch
>
>
> 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:
> # should we make this the default behavior ? (attached patch keeps the
> concurrent flag to true, i.e. the current default behavior)
> # do we use a store for our jobs, should we, especially if we're starting to
> have long-running jobs ?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
