hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (HDFS-3445) If SPNEGO filter fails to initialize, NN should not start
Date Fri, 18 May 2012 20:01:38 GMT

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

Todd Lipcon reassigned HDFS-3445:

    Assignee: Aaron T. Myers
> If SPNEGO filter fails to initialize, NN should not start
> ---------------------------------------------------------
>                 Key: HDFS-3445
>                 URL: https://issues.apache.org/jira/browse/HDFS-3445
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: name-node, security
>    Affects Versions: 2.0.0
>            Reporter: Todd Lipcon
>            Assignee: Aaron T. Myers
>            Priority: Critical
> I recently updated a secure test cluster to trunk which includes the SPNEGO patches for
image transfer, without updating my configuration. Predictably, the HTTP server won't initialize
because I don't have the right principal set up for the server. But, the NameNode started
anyway, and just rejects all image transfer requests with a 503. Instead, it should abort
at startup if the SPNEGO filter fails to init.

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