hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-4249) Add status NameNode startup to webUI
Date Sat, 01 Dec 2012 03:51:58 GMT

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

Andrew Purtell commented on HDFS-4249:
--------------------------------------

+1

Do you think it also makes sense to expose journal state here too? For example, where the
edits are being read/recovered from.  If an external editlog service (eg QJM or BKJM) then
perhaps also it can be interrogated for service specific information (hostnames, instance
health status) which can also be printed as part of NN startup status? Might help reveal issues
or reassure because all the relevant state would be side by side at a glance. 
                
> Add status NameNode startup to webUI 
> -------------------------------------
>
>                 Key: HDFS-4249
>                 URL: https://issues.apache.org/jira/browse/HDFS-4249
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions: 3.0.0
>            Reporter: Suresh Srinivas
>            Assignee: Suresh Srinivas
>
> Currently NameNode WebUI server starts only after the fsimage is loaded, edits are applied
and checkpoint is complete. Any status related to namenode startin up is available only in
the logs. I propose starting the webserver before loading namespace and providing namenode
startup information.
> More details in the next comment.

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

Mime
View raw message