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 "Zhijie Shen (JIRA)" <ji...@apache.org> on 2015/07/02 21:17:04 UTC

[jira] [Updated] (YARN-3881) Writing RM cluster-level metrics

     [ https://issues.apache.org/jira/browse/YARN-3881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Zhijie Shen updated YARN-3881:
------------------------------
    Attachment: metrics.json

> 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
(v6.3.4#6332)