[
https://issues.apache.org/jira/browse/YARN-6578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16004287#comment-16004287
]
Naganarasimha G R commented on YARN-6578:
-----------------------------------------
Hi [~fly_in_gis],
Seems to be a useful feature but only thing is {{ContainerStatus}} is
also used to report the container status to RM as part of NM heartbeat also. So
you want to query as part of each NM heartbeat or you want to modify only
{{NMClient.getContainerStatus}} ? Or you plan to update the usage in
ContainerMonitor thread for each container so that it can be picked for both?
IMO it would good to fetch the usage only on {{NMClient.getContainerStatus}}
as, though now we have only CPU and mem but in future there can be more
resource type to monitor.
> 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: [email protected]
For additional commands, e-mail: [email protected]
