[
https://issues.apache.org/jira/browse/YUNIKORN-839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17411021#comment-17411021
]
Wilfred Spiegelenburg commented on YUNIKORN-839:
------------------------------------------------
The second problem I see with the current structure is that there is no real
definition of the usage of the node is. A node can be in the bottom 10% for all
resources while it is 99% full for one resource. Looking at the usage details
based on the resource like this is not adding a lot of useful information.
Useful would be I think to display, as a percentage, the usage per resource for
a node.
> getNodesUtilJSON is broken
> --------------------------
>
> Key: YUNIKORN-839
> URL: https://issues.apache.org/jira/browse/YUNIKORN-839
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: core - common
> Affects Versions: 0.10
> Reporter: Wilfred Spiegelenburg
> Priority: Critical
>
> In {{getNodesUtilJSON()}} is only calculated for resources that are defined
> on a partition level. These might be the same resources as defined in the
> nodes or they might not be.
> When walking over the node the last node visited will ultimately set the
> {{resourceExists}} flag. If I have a set of 2 nodes one that has the resource
> GPU defined and one that has not the outcome of the call will be different
> for the order the nodes get visited.
> If the node with GPU is visited last the second loop will be entered with
> {{resourceExists}} true if it was checked first {{resourceExists}} will be
> false.
> That means the output of the call is unreliable, it also means that any web
> UI parts that display the details cannot be relied on.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
