[
https://issues.apache.org/jira/browse/YARN-6578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16004415#comment-16004415
]
Yang Wang commented on YARN-6578:
---------------------------------
[~Naganarasimha], thanks for your reply.
I plan to get usage from ContainerMetrics and return in ContainerStatus.
If you worry about this will make the NM heartbeat getting bigger, we could set
the utilization only in the response of NMClient.getContainerStatus.
{code}
ContainerImpl.cloneAndGetContainerStatus()
...
ContainerMetrics metrics =
ContainerMetrics.getContainerMetrics(this.containerId);
if (metrics != null) {
status.setUtilization(ResourceUtilization
.newInstance((int) metrics.pMemMBsStat.lastStat().mean(), 0,
(float) metrics.cpuCoreUsagePercent.lastStat().mean()));
} else {
status.setUtilization(ResourceUtilization.newInstance(0, 0, 0));
}
...
{code}
> Return container resource utilization from NM ContainerStatus call
> ------------------------------------------------------------------
>
> Key: YARN-6578
> URL: https://issues.apache.org/jira/browse/YARN-6578
> Project: Hadoop YARN
> Issue Type: New Feature
> Reporter: Yang Wang
>
> When the applicationMaster wants to change(increase/decrease) resources of an
> allocated container, resource utilization is an important reference indicator
> for decision making. So, when AM call NMClient.getContainerStatus, resource
> utilization needs to be returned.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
