[ https://issues.apache.org/jira/browse/SLING-9905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17513811#comment-17513811 ]
Carsten Ziegeler commented on SLING-9905: ----------------------------------------- [~stefanegli] You are right, it can happen that the folder has sub folders ; so we have to go down into the tree and and basically check if there are any jobs in sub folders; if not we can remove the whole tree. I also agree that it makes sense to only partially delete on every run, And yes, tests would be great :) I'm not sure if I have time to look into all of this in the next days; feel free to get started :) > Provide option to include sling instance id nodes in cleanup > ------------------------------------------------------------ > > Key: SLING-9905 > URL: https://issues.apache.org/jira/browse/SLING-9905 > Project: Sling > Issue Type: Improvement > Components: Event > Reporter: Carsten Ziegeler > Assignee: Carsten Ziegeler > Priority: Major > Fix For: Event 4.3.2 > > > Currently, empty nodes for Sling job handling are removed, up to the JCR node > specific to a Sling instance id. That node is kept in place to avoid > unnecessary removal and recreation. > This assumes that the instances are stable and do not frequently change. > However, in volatile installations where new instances are constantly created > (and old ones stopped), this leads to a growing number of nodes for each id > ever started. > One way would be to provide a "idle timeout" configuration - for an instance > id it is recorded when it was first not seen anymore and if it is not seen > for the configured time, these nodes get removed. For example, if the timeout > is set to one day, such nodes are removed approximately one day after the > instance was stopped. > There are probably other ways to fix this -- This message was sent by Atlassian Jira (v8.20.1#820001)