Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Sat, 1 Dec 2012 03:51:58 +0000 (UTC)
From: "Andrew Purtell (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <1036577191.48345.1354333918686.JavaMail.jiratomcat@arcas>
In-Reply-To: <204128371.45990.1354298159109.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (HDFS-4249) Add status NameNode startup to webUI
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


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

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

+1

Do you think it also makes sense to expose journal state here too? For exam=
ple, where the edits are being read/recovered from. =C2=A0If an external ed=
itlog 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.=
=C2=A0
               =20
> Add status NameNode startup to webUI=20
> -------------------------------------
>
>                 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 namenod=
e startin up is available only in the logs. I propose starting the webserve=
r 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 administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira