[ 
https://issues.apache.org/jira/browse/YARN-10702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17303809#comment-17303809
 ] 

Qi Zhu edited comment on YARN-10702 at 3/18/21, 3:15 AM:
---------------------------------------------------------

Thanks [~Jim_Brennan] for this.

It makes sense to me, and it's a very good improvement for big cluster.

I added this to a sub task to event improvement YARN-10695 Event related 
improvement of YARN for better usage.

The patch LGTM with minor things:

We'd better rename getrmEventProcCPUAvg to  getRmEventProcCPUAvg,  
setrmEventProcCPUAvg ... are same.

Thanks.


was (Author: zhuqi):
Thanks [~Jim_Brennan] for this.

It makes sense to me, and it's a very good improvement for big cluster.

I added this to a sub task to event improvement YARN-10695 Event related 
improvement of YARN for better usage.

Thanks.

> 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
>         Attachments: Scheduler-Busy.png, YARN-10702.001.patch, 
> YARN-10702.002.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

Reply via email to