[
https://issues.apache.org/jira/browse/HDFS-4320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mostafa Elhemali updated HDFS-4320:
-----------------------------------
Attachment: HDFS-4320.branch-1.3.patch
Thanks Suresh - updated the patch with unit test and documentation in
hdfs-default. This is the documentation I have - does it sound good?
{code}
<property>
<name>dfs.namenode.rpc-address</name>
<value></value>
<description>
RPC address that handles all clients requests. If empty then we'll get the
value from fs.default.name.
The value of this property will take the form of hdfs://nn-host1:rpc-port.
</description>
</property>
{code}
> NameNode tries to get its address by looking at fs.default.name instead of
> its own config keys
> ----------------------------------------------------------------------------------------------
>
> Key: HDFS-4320
> URL: https://issues.apache.org/jira/browse/HDFS-4320
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 1.1.0
> Reporter: Mostafa Elhemali
> Attachments: HDFS-4320.branch-1.2.patch, HDFS-4320.branch-1.3.patch,
> HDFS-4320.patch, HDFS-4320.trunk.2.patch, HDFS-4320.trunk.patch
>
>
> When NameNode starts up, it tries to find out its address by looking at the
> fs.default.name configuration key instead of using its own keys. This breaks
> scenarios where we try to configure a Hadoop cluster that uses a different
> default file system than DFS, but still try to prop up namenode and datanode
> services as a secondary file system.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
