You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2008/06/03 08:54:45 UTC
[jira] Created: (SLING-498) Execute jobs only on the instance they
were created on
Execute jobs only on the instance they were created on
------------------------------------------------------
Key: SLING-498
URL: https://issues.apache.org/jira/browse/SLING-498
Project: Sling
Issue Type: New Feature
Components: Event
Affects Versions: 2.0.0
Reporter: Carsten Ziegeler
In a clustered environment a job might be executed by the first free node. Usually this should not cause any problems as the job event should contain all necessary information. However in some cases it might not be possible/feasible to put all information into the event. In these cases the job is usually only executable on the cluster node where the job has been created.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-498) Execute jobs only on the instance they
were created on
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler closed SLING-498.
----------------------------------
Resolution: Fixed
Add new property EventUtil.PROPERTY_JOB_RUN_LOCAL: if this is specified, the job is only executed on the instance it was created on.
> Execute jobs only on the instance they were created on
> ------------------------------------------------------
>
> Key: SLING-498
> URL: https://issues.apache.org/jira/browse/SLING-498
> Project: Sling
> Issue Type: New Feature
> Components: Event
> Affects Versions: Extensions Event 2.0.2
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Extensions Event 2.0.4
>
>
> In a clustered environment a job might be executed by the first free node. Usually this should not cause any problems as the job event should contain all necessary information. However in some cases it might not be possible/feasible to put all information into the event. In these cases the job is usually only executable on the cluster node where the job has been created.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-498) Execute jobs only on the instance they
were created on
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler updated SLING-498:
-----------------------------------
Affects Version/s: (was: 2.0.0)
Extensions Event 2.0.2
Fix Version/s: Extensions Event 2.0.4
Assignee: Carsten Ziegeler
> Execute jobs only on the instance they were created on
> ------------------------------------------------------
>
> Key: SLING-498
> URL: https://issues.apache.org/jira/browse/SLING-498
> Project: Sling
> Issue Type: New Feature
> Components: Event
> Affects Versions: Extensions Event 2.0.2
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Extensions Event 2.0.4
>
>
> In a clustered environment a job might be executed by the first free node. Usually this should not cause any problems as the job event should contain all necessary information. However in some cases it might not be possible/feasible to put all information into the event. In these cases the job is usually only executable on the cluster node where the job has been created.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.