Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Fri, 18 May 2012 20:01:38 +0000 (UTC)
From: "Todd Lipcon (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <4529958.15949.1337371298134.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1490055028.15896.1337370788968.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Assigned] (HDFS-3445) If SPNEGO filter fails to initialize,
 NN should not start
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ 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