[
https://issues.apache.org/jira/browse/HDFS-5128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13750649#comment-13750649
]
Kihwal Lee commented on HDFS-5128:
----------------------------------
[~daryn] I didn't do that because NN UI and NameNodeRegistration will show its
identity as "0.0.0.0:8020" if the bind address is 0.0.0.0, even if its rpc
address is set to something other than 0.0.0.0. I think NN should show the
"representative" RPC address when one is set, regardless of the bind address.
> Allow multiple net interfaces to be used with HA namenode RPC server
> --------------------------------------------------------------------
>
> Key: HDFS-5128
> URL: https://issues.apache.org/jira/browse/HDFS-5128
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Kihwal Lee
> Assignee: Kihwal Lee
> Priority: Critical
> Attachments: HDFS-5128.branch-2.patch, HDFS-5128.branch-2.v2.patch,
> HDFS-5128-example.patch, HDFS-5128.trunk.patch, HDFS-5128.trunk.v2.patch
>
>
> With the new RPCv9, NN RPC server can be bound to multiple IP addresses and
> serve clients connecting to different addressed using the same SPN. But the
> only way to have NN bind to multiple addresses is to set its RPC address to
> 0.0.0.0. This does not work well with HA especially when name nodes share the
> same config.
> I propose a new option for NN rpc server to bind to all interfaces,
> independent of the rpc address configuration.
--
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
