Return-Path: X-Original-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 14F2D1038E for ; Thu, 20 Jun 2013 05:16:30 +0000 (UTC) Received: (qmail 14146 invoked by uid 500); 20 Jun 2013 05:16:26 -0000 Delivered-To: apmail-hadoop-hdfs-dev-archive@hadoop.apache.org Received: (qmail 14026 invoked by uid 500); 20 Jun 2013 05:16:24 -0000 Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-dev@hadoop.apache.org Delivered-To: mailing list hdfs-dev@hadoop.apache.org Received: (qmail 13987 invoked by uid 99); 20 Jun 2013 05:16:23 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Jun 2013 05:16:23 +0000 Date: Thu, 20 Jun 2013 05:16:23 +0000 (UTC) From: "Suresh Srinivas (JIRA)" To: hdfs-dev@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HDFS-4921) Create a web page to display the namenode features and whether they are turned on or off MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Suresh Srinivas created HDFS-4921: ------------------------------------- Summary: Create a web page to display the namenode features and whether they are turned on or off 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 The only way to determine a feature is turned on or off is to look at namenode logs or configuration. Some time 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 if a 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