[
https://issues.apache.org/jira/browse/HADOOP-9562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13657413#comment-13657413
]
Chris Nauroth commented on HADOOP-9562:
---------------------------------------
{quote}
I'd like to have error codes in the pages, so I can do a curl -m 60
http://namenode:50020/service/dfslive.jsp and expect an error code if dfs is
not up and out out of safemode. The use case would be : let bash scripts (inc
Linux HA scripts) verify FS is live just by looking at the return code of curl
or GET.
{quote}
One difficulty is that we don't start the HTTP server until relatively late in
initialization. If you have a ton of edits, then you'll suffer through a long
checkpoint before status is visible, either in the web page or a REST
interface. I have patches queued up in HDFS-4249 and its sub-tasks to start
the HTTP server sooner and display more details about the early phases of
namenode startup.
> Create REST interface for HDFS health data
> ------------------------------------------
>
> Key: HADOOP-9562
> URL: https://issues.apache.org/jira/browse/HADOOP-9562
> Project: Hadoop Common
> Issue Type: New Feature
> Components: fs
> Affects Versions: 2.0.4-alpha
> Reporter: Trevor Lorimer
> Priority: Minor
>
> 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
