hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Akira AJISAKA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-6350) Documenting Hadoop metrics
Date Tue, 10 Jun 2014 22:59:02 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-6350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14027177#comment-14027177

Akira AJISAKA commented on HADOOP-6350:

bq. These are not actually metrics. These are not collected or sinked by MetricsSystem, so
users cannot get them by file or ganglia. Users can get these information only by jmx/jconsole.
However, we should document these information also. I'll create a separate jira for tracking

bq. As a separate discussion I think long term maintenance of this documentation will be challenging.

I agree with you. If this document includes the information registered to MBeans (which can
be accessed via jmx or jconsole), the maintenance will get more challenging. 

> Documenting Hadoop metrics
> --------------------------
>                 Key: HADOOP-6350
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6350
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: documentation, metrics
>    Affects Versions: 3.0.0, 2.1.0-beta
>            Reporter: Hong Tang
>            Assignee: Akira AJISAKA
>              Labels: metrics
>         Attachments: HADOOP-6350-sample-1.patch, HADOOP-6350-sample-2.patch, HADOOP-6350-sample-3.patch,
HADOOP-6350.4.patch, HADOOP-6350.5.patch, HADOOP-6350.6.patch, HADOOP-6350.7.patch, sample1.png
> Metrics should be part of public API, and should be clearly documented similar to HADOOP-5073,
so that we can reliably build tools on top of them.

This message was sent by Atlassian JIRA

View raw message