Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
2.0.0-alpha
-
None
-
None
Description
When the NameNode is started it listens on two addresses. One defined by "dfs.namenode.servicerpc-address" and the other is derived from fs.defaultFS. It seems like it should check to see if "dfs.namenode.rpc-address" is set to match how getServiceRpcServerAddress.
I have written a patch which updates getRpcServerAddress to achieve this. This means you can set fs.defaultFS to hdfs://hostname/ then set dfs.namenode.rpc-address to 0.0.0.0:8020 and the NameNode will listen on all IP addresses on that machine.