[
http://jira.magnolia-cms.com/browse/MGNLSCH-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ondřej Chytil updated MGNLSCH-15:
---------------------------------
Assignee: Ondřej Chytil
Fix Version/s: 1.4.3
(was: 1.4.x)
> Allow tasks to specify cluster node on which to run in clustered
> configurations
> -------------------------------------------------------------------------------
>
> Key: MGNLSCH-15
> URL: http://jira.magnolia-cms.com/browse/MGNLSCH-15
> Project: Magnolia Scheduler Module
> Issue Type: Improvement
> Affects Versions: 1.3
> Reporter: Jan Haderka
> Assignee: Ondřej Chytil
> Priority: Major
> Fix For: 1.4.3
>
> Attachments: AbstractClusterLockCommand.java
>
>
> Right now when running Magnolia in fully clustered environment (i.e. with
> clustered {{config}} workspace) scheduled tasks are launched on all nodes.
> This leads to problems when such tasks include content modification and
> locking. It should be possible to specify at which node such tasks should run
> or at least say whether to run on all or only on one.
--
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/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
