[YARN-7784] Fix Cluster metrics when placement processor is enabled

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.1.0
• Component/s: metrics, RM
• Target Version/s: 3.1.0
• Assignee: Arun Suresh
• Reporter: Weiwei Yang
• Created: 22/Jan/18 11:35
• Updated: 31/Jan/18 17:35
• Resolved: 26/Jan/18 05:28

Description

Reproducing steps

1. Setup a cluster and sets yarn.resourcemanager.placement-constraints.enabled to true
2. Submit a DS job with placement constraint, such as -placement_spec foo=2,NOTIN,NODE,foo
3. 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.