[
https://issues.apache.org/jira/browse/YARN-10702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Badger updated YARN-10702:
-------------------------------
Fix Version/s: 3.2.3
3.1.5
Thanks for the additional patches, [~Jim_Brennan]. I committed the 3.2 and 3.1
patches. This has now been committed to trunk (3.4), branch-3.3, branch-3.2,
and branch-3.1.
> Add cluster metric for amount of CPU used by RM Event Processor
> ---------------------------------------------------------------
>
> Key: YARN-10702
> URL: https://issues.apache.org/jira/browse/YARN-10702
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: yarn
> Affects Versions: 2.10.1, 3.4.0
> Reporter: Jim Brennan
> Assignee: Jim Brennan
> Priority: Minor
> Fix For: 3.4.0, 3.3.1, 3.1.5, 3.2.3
>
> Attachments: Scheduler-Busy.png, YARN-10702-branch-3.1.006.patch,
> YARN-10702-branch-3.2.006.patch, YARN-10702-branch-3.3.006.patch,
> YARN-10702.001.patch, YARN-10702.002.patch, YARN-10702.003.patch,
> YARN-10702.004.patch, YARN-10702.005.patch, YARN-10702.006.patch,
> simon-scheduler-busy.png
>
>
> Add a cluster metric to track the cpu usage of the ResourceManager Event
> Processing thread. This lets us know when the critical path of the RM is
> running out of headroom.
> This feature was originally added for us internally by [~nroberts] and we've
> been running with it on production clusters for nearly four years.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
