[
https://issues.apache.org/jira/browse/YUNIKORN-949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17479712#comment-17479712
]
Peter Bacsko 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?"
It's certainly an extra step that they need to perform and depending on the
environment, it might not be an option, I don't know. But from the perspective
of YK, it's just a path, so if it's not hard-coded like right now, it's already
a good enhancement.
But I agree that leaving the amount of data growing unchecked is potentially
dangerous.
> 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]
