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 Tue, 05 Nov 2013 06:48:17 GMT

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

Vivek Ganesan commented on HDFS-4921:

Do we need a separate page for this? or do we need a unified REST API?

> 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 was sent by Atlassian JIRA

View raw message