[ 
https://issues.apache.org/jira/browse/HDFS-5128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13749511#comment-13749511
 ] 

Philip Zeyliger commented on HDFS-5128:
---------------------------------------

It would be slightly more consistent to expose this as "rpc bind address" and 
have users specify 0.0.0.0 if they want to bind to the wildcard.  The existing 
bug and bad behavior is because {{dfs.namenode.servicerpc-address}} doubles as 
both the address that clients should use to connect and the address that the 
server should bind on.  If you want to be fully flexible, you may as well 
separate those two.  Introducing a toggle for "bind to wildcard" is certainly 
clear (and, in fact, it's exactly the toggle that we try to expose in Cloudera 
Manager as a general practice), but since many other addresses in the Hadoop 
ecosystem already require you to specify 0.0.0.0 to bind to the wildcard (e.g., 
that's what you do for the datanode), it might be more consistent to have a 
bind address config option.
                
> 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.trunk.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

Reply via email to