You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Timothee Maret (Jira)" <ji...@apache.org> on 2020/01/30 09:13:00 UTC

[jira] [Commented] (SLING-9039) The PackageCleanupTask may never run in k8s deployments

    [ https://issues.apache.org/jira/browse/SLING-9039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17026529#comment-17026529 ] 

Timothee Maret commented on SLING-9039:
---------------------------------------

Fixed in [05347db39306554539fd909b4b05b8782f7df967|https://github.com/apache/sling-org-apache-sling-distribution-journal/commit/05347db39306554539fd909b4b05b8782f7df967] by making sure the task runs upon activate.

> The PackageCleanupTask may never run in k8s deployments
> -------------------------------------------------------
>
>                 Key: SLING-9039
>                 URL: https://issues.apache.org/jira/browse/SLING-9039
>             Project: Sling
>          Issue Type: Bug
>          Components: Content Distribution
>    Affects Versions: Content Distribution Journal Core 0.1.6
>            Reporter: Timothee Maret
>            Assignee: Timothee Maret
>            Priority: Major
>             Fix For: Content Distribution Journal Core 0.1.8
>
>
> With SLING-8969 the delay between two runs of the package cleanup task has been set to 7 days. That makes sense however in practice the task may never run unless the service is kept alive for 7 days. In cloud deployments where we treat services as cattle there likely are no service alive for that long.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)