You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2014/02/14 05:57:19 UTC

[jira] [Commented] (HDFS-5943) 'dfs.namenode.https-address.ns1' property is not used in federation setup

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

Hadoop QA commented on HDFS-5943:
---------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12628868/HDFS-5943.1.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of javac compiler warnings.

    {color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

    {color:green}+1 eclipse:eclipse{color}.  The patch built with eclipse:eclipse.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new Findbugs (version 1.3.9) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:red}-1 core tests{color}.  The patch failed these unit tests in hadoop-hdfs-project/hadoop-hdfs:

                  org.apache.hadoop.hdfs.server.namenode.ha.TestHASafeMode

    {color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/6151//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/6151//console

This message is automatically generated.

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