[
https://issues.apache.org/jira/browse/SLING-3392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13905372#comment-13905372
]
Carsten Ziegeler commented on SLING-3392:
-----------------------------------------
After checking the code I think we can do the following:
traverse the repository instead of doing a search
use batch deletion
decrease the TTL for locks to two minutes
do the lock cleanup every minute
I don't see any way to not create a flat hierarchy which leaves us with an
equally distributed hierarchy
> JobManager MaintenanceTask should not rely on search for removing locks
> -----------------------------------------------------------------------
>
> Key: SLING-3392
> URL: https://issues.apache.org/jira/browse/SLING-3392
> Project: Sling
> Issue Type: Bug
> Components: Extensions
> Affects Versions: Event 3.3.4
> Reporter: Amit Gupta
> Assignee: Carsten Ziegeler
> Fix For: Event 3.3.6
>
>
> org.apache.sling.event.impl.jobs.MaintenanceTask relies on search to find
> obsolete locks and remove those.
> Search can fail for reasons such as index corruption. It should not rely on
> search for such critical tasks.
> And, another issue with locks is that those are created in a flat hierarchy.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
