[
https://issues.apache.org/jira/browse/YUNIKORN-949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17479651#comment-17479651
]
Anuraag Nalluri commented on YUNIKORN-949:
------------------------------------------
Wouldn’t it be a burden for a user to have to configure an external volume just
to store the dump output files? Also, limitations would still be needed. We’re
adding ~2MB every 3 or 4 output files even on a small docker desktop cluster
with 4 applications (example sleep + Nginx). If the volume is backed by 100GB
EFS share on EKS, accidentally leaving periodic dump on a large cluster with
the default dump period may max out the volume within 2 weeks.
I’ll send a PR to make the path configurable and include a parameter for
limiting number of output files for the rolling approach you mentioned above.
But still looking for any advice on what a reasonable default may be if the
user does not specify the number of files. It seems like a complicated knob for
most users who want to debug Yunikorn to handle since they may not be aware of
the memory details of their cluster.
> 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]
