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

Hudson commented on HADOOP-14867:
---------------------------------

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #12864 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/12864/])
HADOOP-14867. Update HDFS Federation setup document, for incorrect (arp: rev 
f153e60576016ddc237aa66eb36e2c2c91efdbf3)
* (edit) hadoop-hdfs-project/hadoop-hdfs/src/site/markdown/Federation.md


> 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
>             Fix For: 2.9.0, 3.0.0-beta1, 2.8.3, 2.7.5
>
>         Attachments: HADOOP-14867.patch
>
>
> HDFS Federation setup documentation is having incorrect property name for 
> secondary namenode http port
> It is mentioned as 
> {code}
> <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>
> {code}
> 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 throw's an exception 



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to