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

Trevor Lorimer commented on HADOOP-9562:
----------------------------------------

Hi, Thanks Philip about 75% of the information can be obtained from JMX.

I only need to make these additions to pre-existing JMX interfaces (I will link 
this to a new JIRA):
Started time,
Compiled info,
Jvm MaxHeap, MaxNonHeap
Node Usage stats (i.e. Min, Median, Max, stdev),
Number of decommissioned Live and Dead nodes,
Journal Status

The only information I have had difficulty obtaining is the status header (e.g. 
NameNode 'localhost:8020' (active)). This information is contained within the 
NameNode object which does not seem to be exposed through JMX and cannot be 
referenced from FSNamesystem.

                
> Create REST interface for HDFS health data
> ------------------------------------------
>
>                 Key: HADOOP-9562
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9562
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: fs
>    Affects Versions: 2.0.4-alpha
>            Reporter: Trevor Lorimer
>            Priority: Minor
>         Attachments: 0001-HAD-162-Final-revision-refactor.patch
>
>
> The HDFS health screen (dfshealth.jsp) displays basic Version, Security and 
> Health information concerning the NameNode, currently this information is 
> accessible from classes in the org.apache.hadoop,hdfs.server.namenode package 
> and cannot be accessed outside the NameNode. This becomes prevalent if the 
> data is required to be displayed using a new user interface.
> The proposal is to create a REST interface to expose all the information 
> displayed on dfshealth.jsp using GET methods. Wrapper classes will be created 
> to serve the data to the REST root resource within the hadoop-hdfs project.
> This will enable the HDFS health screen information to be accessed remotely.

--
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

Reply via email to