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] [Commented] (HADOOP-8786) HttpServer continues to start even if AuthenticationFilter fails to init
Date Tue, 11 Sep 2012 04:46:08 GMT

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

Todd Lipcon commented on HADOOP-8786:

It's very similar to HADOOP-7688, but depends on the way in which the filter is initialized.
I'm not super familiar with the Jetty internals, but it looks like this API call is using
FilterHolders instead of FilterInitializers, which perhaps is what causes the difference.

As for whether the start call is synchronous/blocking, it does appear to be. The stack trace
shown in the exception shows the "HttpServer.start()" call on its backtrace, implying that
it's on the same thread.
> HttpServer continues to start even if AuthenticationFilter fails to init
> ------------------------------------------------------------------------
>                 Key: HADOOP-8786
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8786
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 1.2.0, 3.0.0, 2.0.1-alpha
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>         Attachments: hadoop-8786.txt
> As seen in HDFS-3904, if the AuthenticationFilter fails to initialize, the web server
will continue to start up. We need to check for context initialization errors after starting
the server.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message