Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Wed, 15 Feb 2012 00:30:00 +0000 (UTC)
From: "Aaron T. Myers (Commented) (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <1039424152.38783.1329265800676.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1928510094.38478.1329263039593.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HDFS-2950) Secondary NN HTTPS address should be
 listed as a NAMESERVICE_SPECIFIC_KEY
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HDFS-2950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13208155#comment-13208155 ] 

Aaron T. Myers commented on HDFS-2950:
--------------------------------------

+1, patch looks good to me.
                
> Secondary NN HTTPS address should be listed as a NAMESERVICE_SPECIFIC_KEY
> -------------------------------------------------------------------------
>
>                 Key: HDFS-2950
>                 URL: https://issues.apache.org/jira/browse/HDFS-2950
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: name-node
>    Affects Versions: 0.23.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>            Priority: Minor
>         Attachments: hdfs-2950.txt
>
>
> This config was mistakenly left out of the NAMESERVICE_SPECIFIC_KEY map, which makes it tougher to configure federated clusters with security.

--
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