[
https://issues.apache.org/jira/browse/HADOOP-6408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12793620#action_12793620
]
Steve Loughran commented on HADOOP-6408:
----------------------------------------
Servlet serialization is a funny, from the world of shared-state front-end
machines; servlet state can be pushed into some common space so the same
servlet re-used. Normally it exists to stop dynamic webapp reload working under
Tomcat and friends.
Given that configurations don't normally contain security-sensitive data, we
could just ignore the problem here, or possibly consider adding the option to
disable this servlet if you really don't want it. That's much simpler to handle
than filtering content.
> 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.
