[
https://issues.apache.org/jira/browse/HDFS-13533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16468206#comment-16468206
]
Sophie Wang commented on HDFS-13533:
------------------------------------
For example, if you put the configure:
<configuration>
<property>
<name>dfs.nameservices</name>
<value>ns0,ns1,ns2,ns3,ns-fed</value>
</property>
<property>
<name>dfs.ha.namenodes.ns-fed</name>
<value>r1,r2</value>
</property>
<property>
<name>dfs.namenode.rpc-address.ns-fed.r1</name>
<value>router1:rpc-port</value>
</property>
<property>
<name>dfs.namenode.rpc-address.ns-fed.r2</name>
<value>router2:rpc-port</value>
</property>
<property>
<name>dfs.client.failover.proxy.provider.ns-fed</name>
<value>org.apache.hadoop.hdfs.server.namenode.ha.ConfiguredFailoverProxyProvider</value>
</property>
<property>
<name>dfs.client.failover.random.order</name>
<value>true</value>
</property>
</configuration>
In hdfs-site.xml before you start namenode or datanode process, namenode and
datanode would fail to start. I think this is because nn/dn will treat ns-fed
as one of the nameservice and try to connect router1:rpc-port as nn.
This means if I want to use router in nn/dn, I need to change hdfs-site.xml
after the nn/dn started. Otherwise I can not use router in nn/dn
> RBF: Configuration for RBF in namenode/datanode
> -----------------------------------------------
>
> Key: HDFS-13533
> URL: https://issues.apache.org/jira/browse/HDFS-13533
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Sophie Wang
> Priority: Major
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
