[
https://issues.apache.org/jira/browse/HDFS-4249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13615769#comment-13615769
]
Chris Nauroth commented on HDFS-4249:
-------------------------------------
I'm about to post patches on all 3 sub-tasks: HDFS-4372, HDFS-4373, and
HDFS-4374. The patches are separated to try to simplify code review, though it
probably makes sense for code reviewers to give all 3 at least a quick scan.
HDFS-4372 contains the majority of core NameNode changes. HDFS-4373 and
HDFS-4374 contain code for different consumers of the startup progress
information. I've made sure that everyone who is a watcher on HDFS-4249 is
also a watcher on all sub-tasks, so that everyone receives all of the related
updates.
> 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: Chris Nauroth
> 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
