[
https://issues.apache.org/jira/browse/YUNIKORN-949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17479682#comment-17479682
]
Weiwei Yang commented on YUNIKORN-949:
--------------------------------------
{quote}
I’ll send a PR to make the path configurable and include a parameter for
limiting the number of output files for the rolling approach you mentioned
above.
{quote}
+1
is there any available go package for the rolling files?
{quote}
But still looking for any advice on what a reasonable default maybe if the user
does not specify the number of files.
{quote}
We need to do some rough estimation, we can make a dump in a small cluster and
estimate the size for larger clusters. We should look at MBs level files, given
the space in a docker file system is really limited. Maybe 10/20 MB per file,
and limited to several files would be enough. [~pbacsko] , can you help to do
some rough estimate for the size recommendation?
> 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]
