You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Weiwei Yang (JIRA)" <ji...@apache.org> on 2018/01/26 03:20:00 UTC
[jira] [Assigned] (YARN-7784) Cluster metrics is inaccurate when
placement constraint is enabled
[ https://issues.apache.org/jira/browse/YARN-7784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Weiwei Yang reassigned YARN-7784:
---------------------------------
Assignee: Arun Suresh
> 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
> Assignee: Arun Suresh
> Priority: Major
> Attachments: YARN-7784-YARN-6592.001.patch
>
>
> 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: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org