-
Improvement
-
Resolution: Fixed
-
Major
-
1.3
-
None
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.
- is causing
-
MGNLSCH-24 Cluster-aware job functionality can break certain use cases
- Closed
- is duplicated by
-
MGNLSCH-23 Support cluster ID in configuration of scheduled job
- Closed
- is related to
-
DOCU-299 Running scheduled jobs on a particular cluster node
- Closed
-
MGNLSCH-25 It should be possible to run a job on a single node of the cluster without forcing the node id.
- Closed