You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-dev@hadoop.apache.org by "Chris Nauroth (JIRA)" <ji...@apache.org> on 2013/07/12 07:23:50 UTC

[jira] [Resolved] (HDFS-4249) Add status NameNode startup to webUI

     [ https://issues.apache.org/jira/browse/HDFS-4249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Nauroth resolved HDFS-4249.
---------------------------------

       Resolution: Fixed
    Fix Version/s: 2.1.0-beta
                   3.0.0
     Hadoop Flags: Reviewed

All related patches have been committed to trunk, branch-2, branch-2.1-beta, and branch-2.1.0-beta.
                
> Add status NameNode startup to webUI 
> -------------------------------------
>
>                 Key: HDFS-4249
>                 URL: https://issues.apache.org/jira/browse/HDFS-4249
>             Project: Hadoop HDFS
>          Issue Type: New Feature
>          Components: namenode
>    Affects Versions: 3.0.0, 2.1.0-beta
>            Reporter: Suresh Srinivas
>            Assignee: Chris Nauroth
>             Fix For: 3.0.0, 2.1.0-beta
>
>         Attachments: HDFS-4249.1.pdf, HDFS-4249-1.png, HDFS-4249-2.png, HDFS-4249-3.png, HDFS-4249-4.png, HDFS-4249-5.png
>
>
> 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