[
https://issues.apache.org/jira/browse/YUNIKORN-1440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17642146#comment-17642146
]
Brandon Grams commented on YUNIKORN-1440:
-----------------------------------------
With these changes, cleanup would become subject to the cleanupExpiredApps loop
on an interval defined
[here|https://github.com/apache/yunikorn-core/blob/339cc04bfe3dd9eedb386a6f040500d53bea8a46/pkg/scheduler/partition_manager.go#L32].
Apps are eventually expired after 3 days
([link|https://github.com/apache/yunikorn-core/blob/master/pkg/scheduler/objects/application.go#L48]),
so worst case these will hang around for 4 days.
I'd love to externalize these parameters as we'd prefer the most aggressive
setting possible. Can open separate tickets for those.
> Completed applications are indefinitely retained in-memory
> ----------------------------------------------------------
>
> Key: YUNIKORN-1440
> URL: https://issues.apache.org/jira/browse/YUNIKORN-1440
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: core - scheduler
> Affects Versions: 1.1.0
> Reporter: Brandon Grams
> Assignee: Brandon Grams
> Priority: Major
> Labels: pull-request-available
>
> Terminated applications are not considered in the [expired apps cleanup
> procedure|https://github.com/apache/yunikorn-core/blob/c61511fe84a1ae211046aa58f156ac2185892e8f/pkg/scheduler/partition.go#L1425],
> leading to indefinite retention of application objects and eventual memory
> pressure in the scheduler.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
