Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 13 Sep 2017 18:26:00 +0000 (UTC)
From: "Bharat Viswanadham (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.13102021.1505326875000.104645.1505327160051@Atlassian.JIRA>
In-Reply-To: <JIRA.13102021.1505326875000@Atlassian.JIRA>
References: <JIRA.13102021.1505326875000@Atlassian.JIRA> <JIRA.13102021.1505326875206@jira-lw-us.apache.org>
Subject: [jira] [Updated] (HADOOP-14867) Update HDFS Federation setup
 document, for incorrect property name for secondary name node http address
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 13 Sep 2017 18:26:05 -0000


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

Bharat Viswanadham updated HADOOP-14867:
----------------------------------------
    Summary: Update HDFS Federation setup document, for incorrect property name for secondary name node http address  (was: Update HDFS Federation Document, for incorrect property name for secondary name node)

> Update HDFS Federation setup document, for incorrect property name for secondary name node http address
> -------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-14867
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14867
>             Project: Hadoop Common
>          Issue Type: Bug
>            Reporter: Bharat Viswanadham
>            Assignee: Bharat Viswanadham
>
> HDFS Federation setup documentation is having incorrect property name for secondary namenode http port
> It is mentioned as 
> <property>
>     <name>dfs.namenode.secondaryhttp-address.ns1</name>
>     <value>snn-host1:http-port</value>
>   </property>
>   <property>
>     <name>dfs.namenode.rpc-address.ns2</name>
>     <value>nn-host2:rpc-port</value>
>   </property>
> Actual property should be dfs.namenode.secondary.http-address.ns.
> Because of this documentation error, when the document is followed and user tries to setup HDFS federated cluster, secondary namenode will not be started and also 
> hdfs getconf -secondarynamenodes will throw an exception 


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org