[
https://issues.apache.org/jira/browse/YUNIKORN-949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17479126#comment-17479126
]
Weiwei Yang commented on YUNIKORN-949:
--------------------------------------
Hi [~anuraagn] thank you for working on this.
Let's look at the simplest policy for the dump files. I do not have all the
details how the dump files look like, are we creating new files each time? In
this case, the simplest way is to add a config to control the max number of
dump files to store. Users can estimate a reasonable number based on the size
of each file (size will be related to the size of the cluster, num of pods,
etc), and then get some basic limit on the total size. [~pbacsko] , what do you
think?
> Location of the state dump file should be configurable
> ------------------------------------------------------
>
> Key: YUNIKORN-949
> URL: https://issues.apache.org/jira/browse/YUNIKORN-949
> Project: Apache YuniKorn
> Issue Type: Improvement
> Components: core - scheduler
> Reporter: Peter Bacsko
> Assignee: Anuraag Nalluri
> Priority: Major
>
> In YUNIKORN-940, the periodic state dump feature was introduced.
> However, the location of the file is fixed: it's the current working
> directory of the YK scheduler binary. This can become a problem with docker
> containers having a small free space or if the user wants the state to be
> logged frequently.
> The location of the file should be configurable, so it can be written an
> external volume.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
