[
https://issues.apache.org/jira/browse/YARN-10702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17305110#comment-17305110
]
Jim Brennan commented on YARN-10702:
------------------------------------
Thanks for the suggestions [~gandras]! I agree this should be configurable. I
will put up a new patch with those changes.
I don't think the new thread has a significant impact. I wasn't trying to
measure that, but when I was looking at an RM recently where the dispatcher
thread was very busy, the monitoring thread did not appear to be a significant
factor, it was popping up as using less than 10% of a single CPU for brief
periods of time IIRC. I'll have to take a closer look. But I think making the
sampling rate configurable is a good idea.
> 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, YARN-10702.003.patch, YARN-10702.004.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
