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

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.1.0, 2.1.1-beta, 3.0.0-alpha1
• Fix Version/s: 1.2.0
• Component/s: datanode, namenode
• Hadoop Flags: Reviewed

Release Note

The namenode RPC address is currently identified from configuration "fs.default.name". In some setups where default FS is other than HDFS, the "fs.default.name" cannot be used to get the namenode address. When such a setup co-exists with HDFS, with this change namenode can be identified using a separate configuration parameter "dfs.namenode.rpc-address".

"dfs.namenode.rpc-address", when configured, overrides fs.default.name for identifying namenode RPC address.

• Assignee: Mostafa Elhemali
• Reporter: Mostafa Elhemali
• Created: 17/Dec/12 22:09
• Updated: 12/May/16 18:12
• Resolved: 20/Dec/12 22:21

Description

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.