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

Craig Condit resolved YUNIKORN-1385.
------------------------------------
    Fix Version/s: 1.3.0
       Resolution: Fixed

Merged to master. Thanks [~yzhangal] for the contribution.

> To provide visibility to application's aggregated resource consumption
> ----------------------------------------------------------------------
>
>                 Key: YUNIKORN-1385
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-1385
>             Project: Apache YuniKorn
>          Issue Type: New Feature
>          Components: core - common, core - scheduler, shim - kubernetes
>            Reporter: Yongjun Zhang
>            Assignee: Yongjun Zhang
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.3.0
>
>         Attachments: image-2022-11-09-11-06-20-479.png, 
> yunikornResourceUsageVisibility.pdf
>
>
> Currently the "Used Resource" for a given application reported at Yunikorn 
> GUI is actually the snapshot of the resources currently allocated to the 
> application. We need to provide visibility to how much resources an 
> application has used so far, and it would be important to report  how much 
> total resources is used by the application. 
> The unit of resources used can be memoryseconds/vcoreseconds like how Hadoop 
> Yarn does in its app summary report. However, there is more complexity with 
> K8s which supports different instance types (Hadoop Yarn does support 
> multiple instance types but its app summary report ignored instance types). 
> It would be nice to report how much resource is used for each instance types 
> used by an application.
> This is a top level Jira for this new feature. Subtask jira will be created 
> when we work on it.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to