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/09/27 10:25:32 UTC

[jira] Created: (SLING-1807) Don't lock node for local jobs

Don't lock node for local jobs
------------------------------

                 Key: SLING-1807
                 URL: https://issues.apache.org/jira/browse/SLING-1807
             Project: Sling
          Issue Type: Improvement
          Components: Extensions
    Affects Versions: Extensions Event 2.4.0
            Reporter: Carsten Ziegeler
            Assignee: Carsten Ziegeler
            Priority: Minor


Locking is used to avoid processing on several nodes in a clusterd environment. However if the job is marked to run on a specific instance, locking is not needed at all
Avoiding the lock reduces the load on the repository.

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

[jira] Resolved: (SLING-1807) Don't lock node for local jobs

Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SLING-1807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler resolved SLING-1807.
-------------------------------------

    Resolution: Invalid

We can't easily optimize - as configurations might be different in clustered environments and there might be additional problems in the job handling - therefore just closing this

> Don't lock node for local jobs
> ------------------------------
>
>                 Key: SLING-1807
>                 URL: https://issues.apache.org/jira/browse/SLING-1807
>             Project: Sling
>          Issue Type: Improvement
>          Components: Extensions
>    Affects Versions: Extensions Event 2.4.0
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>            Priority: Minor
>
> Locking is used to avoid processing on several nodes in a clusterd environment. However if the job is marked to run on a specific instance, locking is not needed at all
> Avoiding the lock reduces the load on the repository.

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