[
https://issues.apache.org/jira/browse/YARN-3630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14545188#comment-14545188
]
Xianyin Xin commented on YARN-3630:
-----------------------------------
Thanks, [~leftnoteasy] and [~kasha].
[~leftnoteasy], I think {{ScheulerMetrics}} is a good idea, but I think we
should also consider some things:
# {{ScheulerMetrics}} tracks various indexes of a scheduler, but we also have
{{QueueMetrics}}. Not exactly, the {{root.metrics}} gives us most of the
information of the scheduler, then how to deal with the relation between the
two;
# #events waiting for being handled is an important index for evaluating the
scheduler's load, but it is not owned by scheduler, it is maintained by
{{ResourceManager#SchedulerEventDispatcher}}, then who will maintain the
{{ScheulerMetrics}}, the {{SchedulerEventDispatcher}} or the scheduler itself?
From the literal meaning, {{ScheulerMetrics}} should be maintained by scheduler.
Anyway, considering the WebUI improvement you mentioned, a {{ScheulerMetrics}}
is need. Created another jira YARN-3652 to discuss this.
Thanks [~kasha] for valuable suggestions on the policy of determining the
heartbeat interval, in the following days I'll work for a draft.
> YARN should suggest a heartbeat interval for applications
> ---------------------------------------------------------
>
> Key: YARN-3630
> URL: https://issues.apache.org/jira/browse/YARN-3630
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: resourcemanager, scheduler
> Affects Versions: 2.7.0
> Reporter: Zoltán Zvara
> Assignee: Xianyin Xin
> Priority: Minor
>
> It seems currently applications - for example Spark - are not adaptive to RM
> regarding heartbeat intervals. RM should be able to suggest a desired
> heartbeat interval to applications.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
