[
https://issues.apache.org/jira/browse/YARN-7784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335430#comment-16335430
]
Weiwei Yang commented on YARN-7784:
-----------------------------------
Note, this issue only exists in processor patch, when
{{yarn.resourcemanager.placement-constraints.enabled}} sets to {{false}} (the
AppPlacementAllocator approach), this cannot be reproduced.
> Cluster metrics is inaccurate when placement constraint is enabled
> ------------------------------------------------------------------
>
> Key: YARN-7784
> URL: https://issues.apache.org/jira/browse/YARN-7784
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: metrics, RM
> Reporter: Weiwei Yang
> Priority: Major
>
> Reproducing steps
> # Setup a cluster and sets
> {{yarn.resourcemanager.placement-constraints.enabled}} to true
> # Submit a DS job with placement constraint, such as {{-placement_spec
> foo=2,NOTIN,NODE,foo}}
> # Check cluster metrics from http://<RM_ADDRESS>/cluster/apps
> when job is running, {{Containers Running}}, {{Memory Used}} and {{VCore
> Used}} were not updated (except AM), metrics from containers allocated by the
> PlacementProcessor were not accumulated to the cluster metrics; however when
> job is done, the resource were deducted. Then UI displays like following:
> * Containers Running: -2
> * Memory Used: -400
> * VCores Used: -2
> Looks like {{AppSchedulingInfo#updateMetricsForAllocatedContainer}} was not
> called when allocating a container.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
