hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Cutting (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (HADOOP-250) HTTP Browsing interface for DFS Health/Status
Date Mon, 19 Jun 2006 19:08:30 GMT
     [ http://issues.apache.org/jira/browse/HADOOP-250?page=all ]
Doug Cutting resolved HADOOP-250:

    Resolution: Fixed

I just committed this.  I made two additional changes.  In FSNameSystem.java I moved the initialization
of the static variable fsNameSystemObject to before where Jetty is started, since the jsp
pages require a non-null value for this and the servlet init was failing with a null pointer
exception.  I also added an entry to hadoop-default.xml for the new dfs.info.port parameter.

> HTTP Browsing interface for DFS Health/Status
> ---------------------------------------------
>          Key: HADOOP-250
>          URL: http://issues.apache.org/jira/browse/HADOOP-250
>      Project: Hadoop
>         Type: New Feature

>   Components: dfs
>     Versions: 0.3.0
>     Reporter: Devaraj Das
>      Fix For: 0.4.0
>  Attachments: dfshealth.pdf, http_browsing_dfs.new.patch, http_browsing_dfs.patch, http_browsing_dfs.patch,
> A web interface to view the DFS health/status (name and data nodes) is to be created.
User can connect to the webserver on the namenode and a web page will be displayed. The web
page will give some details about that namenode (startup time and the total cluster capacity).
The web page will contain a table of 'live' and 'dead' datanodes. Each live datanode will
be a link to the complete details of the datanode as given by DatanodeInfo (also see DataNodeReport).

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message