hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kihwal Lee (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-5128) Allow multiple net interfaces to be used with HA namenode RPC server
Date Mon, 26 Aug 2013 13:56:52 GMT

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

Kihwal Lee commented on HDFS-5128:

Thanks for the comment, Philip. My initial approach was actually what you suggest, but changed
it to the current form after thinking about its possible use cases. That is certainly more
flexible than a simple toggle switch, but I couldn't come up with a reasonable use case where
it is used for specifying something other than  One advantage of this simple toggle
switch is that it is less error-prone.  

I will post an alternate version of patch following your suggestion. Others can chime in to
help decide which approach is better.
> 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 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

View raw message