hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vivek Ganesan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-4921) Create a web page to display the namenode features and whether they are turned on or off
Date Thu, 22 Aug 2013 13:21:52 GMT

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

Vivek Ganesan commented on HDFS-4921:

Hi Suresh,

There are two URLs which currently give NameNode related info over HTTP.

1. http://namenode:50070/jmx  -- JSON 
2. http://namenode:50070/conf   -- XML

If I correctly understand this issue, the requirement of this JIRA is to create a web page
(HTML), which can take data from the above two sources, parse it, and show the same in a human-readable
and searchable way over HTTP.

Please confirm if my understanding is correct.

Also, since we already have JMX and conf, which are machine-readable, do we need a unified
REST API (as Konstantin suggested) for values from both the above sources?

Vivek Ganesan

> Create a web page to display the namenode features and whether they are turned on or
> ----------------------------------------------------------------------------------------
>                 Key: HDFS-4921
>                 URL: https://issues.apache.org/jira/browse/HDFS-4921
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>    Affects Versions: 3.0.0
>            Reporter: Suresh Srinivas
>            Assignee: Vivek Ganesan
> The only way to determine a feature is turned on or off is to look at namenode logs or
configuration. Some times when features change/modified (short circuit for example), the corresponding
log message changes or goes from info to debug etc. Logs are not a reliable way to programmatically,
for example in tests, to determine if a feature is turned on/off.
> Also when debugging issues, routinely I have to ask for configuration to determine if
the feature is turned on or off and hope that the configuration provided is the correct one
loaded in the namenode.
> While namenode does provide config it has loaded over http, some times either due to
poor documentation or lack of understanding of configuration mechanism, people may not be
able to determine the state of the feature. I propose adding a web page that shows all that
we print today in the logs, that feature status and the corresponding configuration values
and feature status. This should also be made available over JMX and JMX http, just like all
the other namenode webUI info, so that scripts and other programs can consume it.

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

View raw message