hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-6408) Add a /conf servlet to dump running configuration
Date Wed, 09 Dec 2009 22:07:18 GMT

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

Todd Lipcon updated HADOOP-6408:

    Attachment: hadoop-6408.txt

Findbugs pointed out that the conf member of ConfServlet wasn't defined as transient, which
made me do some research and learn that in some rare circumstances, HttpServlets can get serialized.
The recommended place to put state like this is in the ServletContext.

This new patch stores Configuration in ServletContext. It's a bit simpler patch, too, with
fewer changes to HttpServer.

It's tested by unit tests, and I also tested manually by running a namenode built against
this and visually inspecting /conf there.

> 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.

View raw message