[
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
New patch with the following changes:
- Configuration now *always* tracks the "setting resource". The reason for
this change is that, otherwise, it's impossible to dump the "running
configuration" of the server without reloading from disk. If you reload from
disk, you aren't seeing the configuration that's actually governing the
server's behavior, so the servlet's less than useful.
- I don't believe this should be a performance issue, since it only affects
Configuration.set() and other mutators. These calls are not made frequently.
Also, the number of Configuration objects floating around a daemon is
reasonably small compared to its overall RAM usage, so I don't think the memory
overhead will be a problem.
I did not implement access control for the reasons I provided above. Confs are
already leaked in the web UI in the form of job.xml files, and people can use
the Filter mechanism otherwise.
> 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-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.
