[
https://issues.apache.org/jira/browse/YUNIKORN-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17714298#comment-17714298
]
Craig Condit commented on YUNIKORN-1702:
----------------------------------------
I don't think we don't want to follow in YARN's footsteps here - that
functionality bloats memory usage. Having the scheduler focus on what's
currently running instead of what has run in the past (the K8s API server and
external tooling can be used for that) will help keep it lean and efficient.
> Application is removed from Yunikorn UI upon completion, better to keep for
> additional time
> -------------------------------------------------------------------------------------------
>
> Key: YUNIKORN-1702
> URL: https://issues.apache.org/jira/browse/YUNIKORN-1702
> Project: Apache YuniKorn
> Issue Type: Improvement
> Reporter: Yongjun Zhang
> Priority: Major
>
> Application is removed from Yunikorn UI upon completion, better to keep for
> additional time.
> Hadoop Yarn keeps completed applications viewable via UI until its cache is
> full (default is 10000) and then it will evict older applications. Would be
> nice to have a similar behavior with Yunikorn.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]