hadoop-hdfs-issues mailing list archives

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

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

Hadoop QA commented on HDFS-5004:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new or modified
test files.

    {color:red}-1 javac{color:red}.  The patch appears to cause the build to fail.

Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/4739//console

This message is automatically generated.
> 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
>            Assignee: Trevor Lorimer
>             Fix For: 3.0.0, 2.3.0
>         Attachments: HDFS-5004.diff, 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