[jira] [Updated] (SLING-9905) Provide option to include sling instance id nodes in cleanup

["Stefan Egli (Jira)" <ji...@apache.org>]

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

Stefan Egli updated SLING-9905:
-------------------------------
    Fix Version/s:     (was: Event 4.2.24)
                   Event 4.2.26

> 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
>            Priority: Major
>             Fix For: Event 4.2.26
>
>
> 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.3.4#803005)