hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Graves (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-7662) logs servlet should use pathspec of /*
Date Tue, 27 Sep 2011 17:45:45 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-7662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115746#comment-13115746

Thomas Graves commented on HADOOP-7662:

Manual testing done.  This was done in conjunction with MAPREDUCE-2999, which when specifying
a auth filter via hadoop.http.filter.initializers caused the /logs servlet to stop working
for yarn webapps. 

- load up a yarn web page (do for all resource manager, node manager, app master, and job
history).  Verify that going to host:port/logs loads up the logs servlet and calls the AdminAuthorizedServlet
class and you can see the log directory.  verify the other default servlets still work (/stacks,/logLevel,/metrics,/conf,/jmx,/static).

- also test dfshealth.jsp and verify /logs and other default servlets work (/stacks,/logLevel,/metrics,/conf,/jmx,/static).
> logs servlet should use pathspec of /*
> --------------------------------------
>                 Key: HADOOP-7662
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7662
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 0.23.0
>            Reporter: Thomas Graves
>            Assignee: Thomas Graves
>             Fix For: 0.23.0
>         Attachments: HADOOP-7662.patch
> The logs servlet in HttpServer should use a pathspec of /* instead of /.
>       logContext.addServlet(AdminAuthorizedServlet.class, "/*");
> In making the changes for the yarn webapps (MAPREDUCE-2999), I registered a webapp to
use "/".  This blocked the /logs servlet from working.  because both had a pathSpec of "/"
and the guice filter seemed to take precendence.  Changing the pathspec of the logs servlet
to /* fixes the issue.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message