[
http://jira.magnolia-cms.com/browse/DOCU-299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antti Hietala updated DOCU-299:
-------------------------------
Description:
You can target scheduled jobs (tasks) to run on a particular cluster node. This
avoids lockups occurring when two or more jobs try to access the same content.
This feature has been available since Scheduler 1.4.4. Document the feature in
the [Scheduler
module|http://documentation.magnolia-cms.com/modules/scheduler.html].
* The cluster node must be identified by setting a {{magnolia.clusterid}}
property in its {{magnolia.properties}} file. The value can be a literal
cluster name such as {{public123}} or a variable such as {{$\{servername\}}}
* In order to run a job on that cluster node, the job configuration must have a
corresponding {{clusterId}} property. The value must match the value of
{{magnolia.clusterId}}. This means that if you want to run the job on a
particular cluster node, configure the property and set its value in the job.
* The {{clusterId}} property should go under the {{params}} content node, see
example below.
* If a job configuration does not have a {{clusterId}} property, the job will
run on all cluster nodes. This is a fallback mechanism that saves some effort
when you have many cluster nodes. Suppose you need to change a job
configuration and your {{config}} workspace is not clustered. You would have to
change it on every cluster node separately. With the fallback you change it in
one node and leave the {{clusterId}} property out. The job will now run on all
cluster nodes.
* Draw a diagram if it helps.
Example: Setting a cluster ID in magnolia.properties file.
{code}
magnolia.clusterId=public123
{code}
Example: Setting a cluster ID in the job configuration.
{code:xml}
+ modules
+ scheduler
+ config
+ jobs
+ ImportRSSFeeds
+ params
- clusterId = public123
- importer = rssaggregator
- active = true
- active = true
- catalog = data
- command = import
- cron = 0 0 6 * * *
- description = Update feeds every day at 6 a.m.
{code}
was:
You can target scheduled jobs (tasks) to run on a particular cluster node. This
avoids lockups occurring when two or more jobs try to access the same content.
This feature has been available since Scheduler 1.4.4. Document the feature in
the [Scheduler
module|http://documentation.magnolia-cms.com/modules/scheduler.html].
* The cluster node must be identified by setting a {{magnolia.clusterid}}
property in its {{magnolia.properties}} file. The value can be a literal
cluster name such as {{public123}} or a variable such as {{$\{servername\}}}
* In order to run a job on that cluster node, the job configuration must have a
corresponding {{clusterId}} property. The value must match the value of
{{magnolia.clusterId}}. This means that if you want to run the job on a
particular cluster node, configure the property and set its value in the job.
* The {{clusterId}} property should go under the {{params}} content node, see
example below.
* If a job configuration does not have a {{clusterId}} property, the job will
run on all cluster nodes. This is a fallback mechanism that saves some effort
when you have many cluster nodes. Support you need to change a job
configuration and your {{config}} workspace is not clustered. You would have to
change it on every cluster node separately. With the fallback you change it in
one node and leave the {{clusterId}} property out. The job will now run on all
cluster nodes.
* Draw a diagram if it helps.
Example: Setting a cluster ID in magnolia.properties file.
{code}
magnolia.clusterId=public123
{code}
Example: Setting a cluster ID in the job configuration.
{code:xml}
+ modules
+ scheduler
+ config
+ jobs
+ ImportRSSFeeds
+ params
- clusterId = public123
- importer = rssaggregator
- active = true
- active = true
- catalog = data
- command = import
- cron = 0 0 6 * * *
- description = Update feeds every day at 6 a.m.
{code}
> Running scheduled jobs on a particular cluster node
> ---------------------------------------------------
>
> Key: DOCU-299
> URL: http://jira.magnolia-cms.com/browse/DOCU-299
> Project: Documentation
> Issue Type: New Feature
> Security Level: Public
> Components: content
> Reporter: Antti Hietala
> Assignee: Gavan Stockdale
>
> You can target scheduled jobs (tasks) to run on a particular cluster node.
> This avoids lockups occurring when two or more jobs try to access the same
> content. This feature has been available since Scheduler 1.4.4. Document the
> feature in the [Scheduler
> module|http://documentation.magnolia-cms.com/modules/scheduler.html].
> * The cluster node must be identified by setting a {{magnolia.clusterid}}
> property in its {{magnolia.properties}} file. The value can be a literal
> cluster name such as {{public123}} or a variable such as {{$\{servername\}}}
> * In order to run a job on that cluster node, the job configuration must have
> a corresponding {{clusterId}} property. The value must match the value of
> {{magnolia.clusterId}}. This means that if you want to run the job on a
> particular cluster node, configure the property and set its value in the job.
> * The {{clusterId}} property should go under the {{params}} content node, see
> example below.
> * If a job configuration does not have a {{clusterId}} property, the job will
> run on all cluster nodes. This is a fallback mechanism that saves some effort
> when you have many cluster nodes. Suppose you need to change a job
> configuration and your {{config}} workspace is not clustered. You would have
> to change it on every cluster node separately. With the fallback you change
> it in one node and leave the {{clusterId}} property out. The job will now run
> on all cluster nodes.
> * Draw a diagram if it helps.
> Example: Setting a cluster ID in magnolia.properties file.
> {code}
> magnolia.clusterId=public123
> {code}
> Example: Setting a cluster ID in the job configuration.
> {code:xml}
> + modules
> + scheduler
> + config
> + jobs
> + ImportRSSFeeds
> + params
> - clusterId = public123
> - importer = rssaggregator
> - active = true
> - active = true
> - catalog = data
> - command = import
> - cron = 0 0 6 * * *
> - description = Update feeds every day at 6 a.m.
> {code}
--
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]>
----------------------------------------------------------------
