[jira] [Closed] (SLING-10854) Introduce cleanup job of old slingId data in discovery

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

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

Stefan Egli closed SLING-10854.
-------------------------------

> Introduce cleanup job of old slingId data in discovery
> ------------------------------------------------------
>
>                 Key: SLING-10854
>                 URL: https://issues.apache.org/jira/browse/SLING-10854
>             Project: Sling
>          Issue Type: Improvement
>          Components: Discovery
>    Affects Versions: Discovery Oak 1.2.34
>            Reporter: Stefan Egli
>            Assignee: Stefan Egli
>            Priority: Major
>             Fix For: Discovery Oak 1.2.44
>
>          Time Spent: 11h 10m
>  Remaining Estimate: 0h
>
> Discovery.oak stores nodes and properties per slingId under {{/var/discovery/oak}}. In a scenario where the slingIds are stable things are fine. If the slingIds change frequently, old slingId-related data stays as garbage and accumulates.
> We should introduce a cleanup job to delete old slingId data. The leader could execute this to avoid race conditions. We might need to add some additional property to indicate age of slingIds (there's already the {{/var/discovery/oak/clusterInstances/leaderElectionIdCreatedAt}} property which gets updated upon each discovery.oak bundle activation - but it's somewhat indirect. Having a new, dedicated property sounds cleaner (this one could be used to clean up old data though)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)