[
https://issues.apache.org/jira/browse/YUNIKORN-949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17482476#comment-17482476
]
Peter Bacsko commented on YUNIKORN-949:
---------------------------------------
Did some testing regarding JSON sizes. These are from idle clusters:
* 3 nodes: 9533 bytes
* 6 nodes: 11082 bytes
* 9 nodes: 12294 bytes
So, depending on the number of nodes, it's roughly 8600 + (n*460) bytes.
A 100 node cluster would be roughly 54k. On a cluster with this size, a
periodic dump of 60s during a 24 hour period would generate 74MiB of data.
Slightly more if not idle.
I think the 10/10 limit sounds reasonable.
> 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
> Labels: pull-request-available
>
> 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]
