hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Srinivas (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-5943) 'dfs.namenode.https-address.ns1' property is not used in federation setup
Date Thu, 13 Feb 2014 22:08:27 GMT

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

Suresh Srinivas updated HDFS-5943:
----------------------------------

    Status: Patch Available  (was: Open)

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

Mime
View raw message