Bringing this out of the normal JIRA notification spam.

Your opinions are appreciated.

-------- Original Message --------
Subject: [jira] [Commented] (ACCUMULO-1817) Use Hadoop Metrics2
Date: Wed, 3 Dec 2014 17:12:13 +0000 (UTC)
From: Josh Elser (JIRA) <j...@apache.org>
Reply-To: j...@apache.org
To: notificati...@accumulo.apache.org


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

Josh Elser commented on ACCUMULO-1817:
--------------------------------------

One big question that needs to be addressed here is what to do with the existing accumulo-metrics.xml file. Metrics2 expects a hadoop-metrics2*.properties file to be configure the sources (emitters from Accumulo) and sinks (file-based logging, push to Ganglia, etc).

I think, long term, it would be better to solely move to the properties file (standardize on what's going on upstream), but that would cause a little bit of pain for users who expect to configure/control metrics via accumulo-metrics.xml.

Thoughts anyone?

Use Hadoop Metrics2
-------------------

                Key: ACCUMULO-1817
                URL: https://issues.apache.org/jira/browse/ACCUMULO-1817
            Project: Accumulo
         Issue Type: New Feature
           Reporter: Corey J. Nolet
           Assignee: Billie Rinaldi
             Labels: proposed
            Fix For: 1.7.0

         Time Spent: 0.5h
 Remaining Estimate: 0h

We currently expose JMX and it's possible (with external code) to bridge the 
JMX to solutions like Ganglia. It would be ideal if the integration were native 
and pluggable.
Turns out that Hadoop (hdfs, mapred) and HBase has "direct" metrics reporting 
to Ganglia through some nice code provided in Hadoop.
Look into the GangliaContext to see if we can implement Ganglia metrics 
reporting by Accumulo configuration alone.
References: http://wiki.apache.org/hadoop/GangliaMetrics, 
http://hbase.apache.org/metrics.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to