[
https://issues.apache.org/jira/browse/HDFS-5128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13751328#comment-13751328
]
Daryn Sharp commented on HDFS-5128:
-----------------------------------
I guess the only concern I have is that the port on the bind address is
silently ignored (albeit documented). We all know people don't read, so it
would be confusing to the user if they specified a port -- because they
intended to do port forwarding -- but the port is ignored. Specifying a port
becomes valid yet undefined behavior that is problematic if we decide to
support a port in the future. Ie. the user added some port, it's dropped, they
upgrade, now the NN breaks.
I'm fine with the change if the config values for binding are handled as
strings solely representing hostnames. Basically use the conf value exactly as
intended.
> 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
