Return-Path: 
 <hdfs-issues-return-78933-apmail-hadoop-hdfs-issues-archive=hadoop.apache.org@hadoop.apache.org>
X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org
Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 24EB01060F
	for <apmail-hadoop-hdfs-issues-archive@minotaur.apache.org>;
 Sat, 15 Feb 2014 13:33:35 +0000 (UTC)
Received: (qmail 50266 invoked by uid 500); 15 Feb 2014 13:33:24 -0000
Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org
Received: (qmail 50048 invoked by uid 500); 15 Feb 2014 13:33:22 -0000
Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:hdfs-issues-help@hadoop.apache.org>
List-Unsubscribe: <mailto:hdfs-issues-unsubscribe@hadoop.apache.org>
List-Post: <mailto:hdfs-issues@hadoop.apache.org>
List-Id: <hdfs-issues.hadoop.apache.org>
Reply-To: hdfs-issues@hadoop.apache.org
Delivered-To: mailing list hdfs-issues@hadoop.apache.org
Received: (qmail 49949 invoked by uid 99); 15 Feb 2014 13:33:21 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 15 Feb 2014 13:33:21 +0000
Date: Sat, 15 Feb 2014 13:33:21 +0000 (UTC)
From: "Hudson (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12694901.1392255465053.48778.1392471201302@arcas>
In-Reply-To: <JIRA.12694901.1392255465053@arcas>
References: <JIRA.12694901.1392255465053@arcas>
Subject: [jira] [Commented] (HDFS-5943) 'dfs.namenode.https-address.ns1'
 property is not used in federation setup
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


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

Hudson commented on HDFS-5943:
------------------------------

FAILURE: Integrated in Hadoop-Hdfs-trunk #1674 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1674/])
HDFS-5943. 'dfs.namenode.https-address' property is not loaded from configuration in federation setup. Contributed by Suresh Srinivas. (suresh: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1568412)
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/NameNode.java


> 'dfs.namenode.https-address.ns1' property is not used in federation setup
> -------------------------------------------------------------------------
>
>                 Key: HDFS-5943
>                 URL: https://issues.apache.org/jira/browse/HDFS-5943
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Yesha Vora
>            Assignee: Suresh Srinivas
>             Fix For: 2.4.0
>
>         Attachments: HDFS-5943.1.patch, HDFS-5943.patch
>
>
> When federation is ON and two name nodes exist in Cluster, dfs.namenode.https-address property is not being respected when dfs.http.policy= HTTPS_ONLY
> Scenario:
> Pre condition:
> Cluster with one namenode is running. The dfs.namenode.https-address is set to 50701. Namenode UI is accessible at https://NN:50701
> Steps followed:
> 1) Enable Federation and start new NN.
> 2) Set https addresses for both NNs.
> <property><name>dfs.federation.nameservices</name><value>ns1,ns2</value></property>
> <property><name>dfs.namenode.https-address.ns2</name><value>host2:50701</value></property>
> <property><name>dfs.namenode.https-address.ns1</name><value>host1:50701</value></property>
> 3) restart Existing and New namenodes.
> Expected behavior:
> Both the name nodes are expected to be accessed on 50701 port. Instead both the Name nodes start with 50470 port.
> https://NN:50470 



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)