[
https://issues.apache.org/jira/browse/YUNIKORN-1385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17634724#comment-17634724
]
Wilfred Spiegelenburg commented on YUNIKORN-1385:
-------------------------------------------------
{quote}I added a Design Doc link, folks who are interested viewing please
request access.
{quote}
Normally we add a doc open to the world for at least viewing and probably
commenting. There might be other people looking at the Jira that would like to
leave a comment. It should be for everyone to see and if implemented a copy of
the doc will end up as part of the documentation on the website.
{quote}beta.kubernetes.io/instance-type=r5.xlarge
{quote}
Please check the documentation for the
[label|https://kubernetes.io/docs/reference/labels-annotations-taints/#nodekubernetesioinstance-type].
The instance type might be stored in a well defined label the content is not
defined. The cloud provider sets the value. They could set it to any value. It
will also not be set when you run your own K8s instance in your data centre.
I think we need to limit this Jira to a simple setup: track the time an
allocation has been active in (milli) seconds for each resource type based on
the requests. Expose that information in the REST call for the application. An
application can have different sizes allocations it will give an indication of
the overall usage.
That detail will already be difficult enough to interpret. Without knowing if
the allocation has a limit set or not and if the node had CPU and network
bandwidth to spare it will be impossible to compare one allocation to another.
Let alone different runs or different nodes with the same type of allocation.
> 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
> 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]
