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 "Prabha Manepalli (JIRA)" <ji...@apache.org> on 2019/03/07 15:02:00 UTC

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

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

Prabha Manepalli commented on YARN-3881:
----------------------------------------

[~BINGXUE QIU] If you are not currently working on this, Can I take this up now. Thanks.

> 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
>            Priority: Major
>              Labels: YARN-5355
>         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
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org