[
https://issues.apache.org/jira/browse/SLING-9905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17534387#comment-17534387
]
Stefan Egli commented on SLING-9905:
------------------------------------
[~cziegeler], question before I dig into writing a test: IIUC then
* configuration.getLocalJobPath() is {{/var/eventing/jobs/assigned/<slingId>}}
* configuration.getUnassignedJobsPath() is {{/var/eventing/jobs/unassigned}}
So they are not at the same level.
However, the
[code|https://github.com/apache/sling-org-apache-sling-event/blob/86a672566f43704f3fa05f2e83c24f6775ef08c3/src/main/java/org/apache/sling/event/impl/jobs/tasks/CleanUpTask.java#L264]
doesn't seem to distinguish whether it is invoked
* with the
[localJobPath|https://github.com/apache/sling-org-apache-sling-event/blob/master/src/main/java/org/apache/sling/event/impl/jobs/tasks/CleanUpTask.java#L100]
* or with the
[unassignedJobPath|https://github.com/apache/sling-org-apache-sling-event/blob/master/src/main/java/org/apache/sling/event/impl/jobs/tasks/CleanUpTask.java#L102]
So I was wondering if that distinction was missing in fullEmptyFolderCleanup or
if this is by design and I'm overlooking something....
> 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.7#820007)
