[jira] [Updated] (HDFS-4320) Add a separate configuration for namenode rpc address instead of only using fs.default.name

["Chuan Liu (JIRA)" <ji...@apache.org>]

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

Chuan Liu updated HDFS-4320:
----------------------------

    Attachment: HDFS-4320-trunk.3.patch

Attaching a new patch; the fix is the same as previous one only using the existing key "dfs.namenode.rpc-address". I believe this is correct behavior because the error message suggests the address should be "dfs.namenode.rpc-address"  in {{validateConfigurationSettings(final Configuration conf)}} method.
                
> Add a separate configuration for namenode rpc address instead of only using fs.default.name
> -------------------------------------------------------------------------------------------
>
>                 Key: HDFS-4320
>                 URL: https://issues.apache.org/jira/browse/HDFS-4320
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: datanode, namenode
>    Affects Versions: 1.1.0
>            Reporter: Mostafa Elhemali
>            Assignee: Mostafa Elhemali
>             Fix For: 1.2.0
>
>         Attachments: HDFS-4320.branch-1.2.patch, HDFS-4320.branch-1.3.patch, HDFS-4320.patch, HDFS-4320.trunk.2.patch, HDFS-4320-trunk.3.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