Mailing-List: contact yarn-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-dev@hadoop.apache.org
Date: Thu, 2 Jul 2015 19:16:04 +0000 (UTC)
From: "Zhijie Shen (JIRA)" <jira@apache.org>
To: yarn-dev@hadoop.apache.org
Message-ID: <JIRA.12842411.1435864531000.88302.1435864564595@Atlassian.JIRA>
In-Reply-To: <JIRA.12842411.1435864531000@Atlassian.JIRA>
References: <JIRA.12842411.1435864531000@Atlassian.JIRA>
 <JIRA.12842411.1435864531339@arcas>
Subject: [jira] [Created] (YARN-3881) Writing RM cluster-level metrics
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Zhijie Shen created YARN-3881:
---------------------------------

             Summary: 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


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)