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 "Sunil G (JIRA)" <ji...@apache.org> on 2015/05/15 12:06:00 UTC

[jira] [Commented] (YARN-3652) A SchedulerMetrics may be need for evaluating the scheduler's performance

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

Sunil G commented on YARN-3652:
-------------------------------

Hi [~xinxianyin]
This will be a very helpful feature and thanks for working on same.

Few points:
1. *Throughput*: Are you mentioning about #events processed over a period of time? If so, how can we set the timeline by which throughput is calculated (configurable?)?
A clear indicator from this will be like we can predict possible end timeline for the pending events in dispatcher queue. Adding throughput with #no of pending events may give much more better indication about RM overload. 

2. However there are many events coming to scheduler, if possible a filter for the events based on events type may be helpful to give an accuracy for throughout and scheduling delay.

> A SchedulerMetrics may be need for evaluating the scheduler's performance
> -------------------------------------------------------------------------
>
>                 Key: YARN-3652
>                 URL: https://issues.apache.org/jira/browse/YARN-3652
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: resourcemanager, scheduler
>            Reporter: Xianyin Xin
>
> As discussed in YARN-3630, a {{SchedulerMetrics}} may be need for evaluating the scheduler's performance. The performance indexes includes #events waiting for being handled by scheduler, the throughput, the scheduling delay and/or other indicators.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)