Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Message-ID: <477519490.1260396438318.JavaMail.jira@brutus>
Date: Wed, 9 Dec 2009 22:07:18 +0000 (UTC)
From: "Todd Lipcon (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Subject: [jira] Updated: (HADOOP-6408) Add a /conf servlet to dump running
 configuration
In-Reply-To: <757579091.1259791940887.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HADOOP-6408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Todd Lipcon updated HADOOP-6408:
--------------------------------

    Status: Patch Available  (was: Open)

> Add a /conf servlet to dump running configuration
> -------------------------------------------------
>
>                 Key: HADOOP-6408
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6408
>             Project: Hadoop Common
>          Issue Type: New Feature
>    Affects Versions: 0.22.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>             Fix For: 0.22.0
>
>         Attachments: hadoop-6408.txt, hadoop-6408.txt, hadoop-6408.txt, hadoop-6408.txt
>
>
> HADOOP-6184 added a command line flag to dump the running configuration. It would be great for cluster troubleshooting to provide access to this as a servlet, preferably in both JSON and XML formats. But really, any format would be better than nothing. This should/could go into all of the daemons.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.