hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lei Guo (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3881) Writing RM cluster-level metrics
Date Thu, 02 Jul 2015 20:00:05 GMT

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

Lei Guo commented on YARN-3881:

This is an interesting topic, assuming the timeline server provides this support, should Ambari
or other monitoring tool to use this for monitoring purpose? If not, what's the scenario to
write RM related metrics?

> Writing RM cluster-level metrics
> --------------------------------
>                 Key: YARN-3881
>                 URL: https://issues.apache.org/jira/browse/YARN-3881
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>            Reporter: Zhijie Shen
>            Assignee: Zhijie Shen
>         Attachments: metrics.json
> RM has a bunch of metrics that we may want to write into the timeline backend to. I attached
the metrics.json that I've crawled via {{http://localhost:8088/jmx?qry=Hadoop:*}}. IMHO, we
need to pay attention to three groups of metrics:
> 1. QueueMetrics
> 2. JvmMetrics
> 3. ClusterMetrics
> The problem is that unlike other metrics belongs to a single application, these ones
belongs to RM or cluster-wide. Therefore, current write path is not going to work for these
metrics because they don't have the associated user/flow/app context info. We need to rethink
of modeling cross-app metrics and the api to handle them.

This message was sent by Atlassian JIRA

View raw message