You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@yunikorn.apache.org by "Wilfred Spiegelenburg (Jira)" <ji...@apache.org> on 2026/03/24 04:06:00 UTC

[jira] [Resolved] (YUNIKORN-2826) Prune zero-values from node capacity

     [ https://issues.apache.org/jira/browse/YUNIKORN-2826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Wilfred Spiegelenburg resolved YUNIKORN-2826.
---------------------------------------------
    Fix Version/s: 1.9.0
       Resolution: Fixed

Total resources gets pruned, other resources are not pruned (like availableResources) as a zero value is correct in those trackers. A node can run out of a resource and thus have zero available. For that case we really want to show the zero.

> Prune zero-values from node capacity
> ------------------------------------
>
>                 Key: YUNIKORN-2826
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-2826
>             Project: Apache YuniKorn
>          Issue Type: Improvement
>          Components: core - scheduler
>            Reporter: Craig Condit
>            Assignee: Po Han Huang
>            Priority: Major
>              Labels: newbie, pull-request-available
>             Fix For: 1.9.0
>
>
> YUNIKORN-2796 added pruning of zero-valued resources in certain cases. We should also do this with node capacity. There are often several resource types which appear with 0 capacity. We should prune this whenever they are set.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: dev-help@yunikorn.apache.org