Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Message-ID: <1873808904.1261617869506.JavaMail.jira@brutus>
Date: Thu, 24 Dec 2009 01:24:29 +0000 (UTC)
From: "Dmytro Molkov (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Subject: [jira] Created: (HADOOP-6470) JMX Context for Metrics
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

JMX Context for Metrics
-----------------------

                 Key: HADOOP-6470
                 URL: https://issues.apache.org/jira/browse/HADOOP-6470
             Project: Hadoop Common
          Issue Type: New Feature
            Reporter: Dmytro Molkov


The way metrics are currently exposed to the JMX in the NameNode is not helpful, since only the current counters in the record can be fetched and without any context those number mean little.
For example the number of files created equal to 150 only means that in the last period there were 150 files created but when the new period will end is unknown so fetching 150 again will either mean another 150 files or we are fetching the same time period.

One of the solutions for this problem will be to have a JMX context that will accumulate the data (being child class of AbstractMetricsContext) and expose different records to the JMX through custom MBeans. This way the information fetched from the JMX will represent the state of things in a more meaningful way.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.