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 2010/10/15 14:54:37 UTC

[jira] Closed: (SLING-1754) Jobs nodes should be unlocked after they have been changed

     [ https://issues.apache.org/jira/browse/SLING-1754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler closed SLING-1754.
-----------------------------------


> Jobs nodes should be unlocked after they have been changed
> ----------------------------------------------------------
>
>                 Key: SLING-1754
>                 URL: https://issues.apache.org/jira/browse/SLING-1754
>             Project: Sling
>          Issue Type: Improvement
>          Components: Extensions
>    Affects Versions: Extensions Event 2.4.0
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: Extensions Event 2.4.2
>
>
> In a clustered environment, it can currently happen that another cluster node picks up a job during the unlock operation in finishJob and tries to process it. There is a delay between the unlock and a remove/finish operation. 
> Therefore the node should either be directly removed/updated before the unlock

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.