hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Luke Lu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-5004) Add additional JMX bean for NameNode status data
Date Fri, 19 Jul 2013 10:22:49 GMT

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

Luke Lu commented on HDFS-5004:

You might want to change the stability to "Evolving" for the newly introduced interface. We
can mark it stable later. Otherwise, this is a reasonable approach (introduce a new status
> Add additional JMX bean for NameNode status data
> ------------------------------------------------
>                 Key: HDFS-5004
>                 URL: https://issues.apache.org/jira/browse/HDFS-5004
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: namenode
>    Affects Versions: 3.0.0, 2.1.0-beta, 2.0.4-alpha
>            Reporter: Trevor Lorimer
>             Fix For: 3.0.0, 2.3.0
>         Attachments: HDFS-5004.diff
> Currently the JMX beans returns much of the data contained on the HDFS Health webpage
(dfsHealth.html). However there are several other attributes that are required to be added,
that can only be accessed from within NameNode.
> For this reason a new JMX bean is required (NameNodeStatusMXBean) which will expose the
following attributes in NameNode:
> Role
> State
> HostAndPort
> also a list of the corruptedFiles should be exposed by NameNodeMXBean.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message