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

Konstantin Shvachko commented on HDFS-13566:
--------------------------------------------

We spent some time thinking and discussing the configuration parameters for 
additional ports. Making NN listening on multiple ports in general seems like a 
reasonable improvement. For encryption we just need one additional port, but 
people may use multiple ports to apply different rules / policies to them.
 The complexity here is that we should support three cases: single NameNode, 
Federated, and HA NameNodes. In the most general case with Federation and HA 
the rpc address is specified like this:
{code:java}
<property>
  <name>dfs.namenode.rpc-address.namespace2.namenode7</name>
  <value>nn7-host:port</value>
</property>
{code}
The idea is to introduce another parameter 
{{dfs.namenode.rpc-address.auxiliary-ports}}, which conforms to the same 
pattern as the {{dfs.namenode.rpc-address}} that is in case of federated HA 
NameNode looks like this:
{code:java}
<property>
  <name>dfs.namenode.rpc-address.auxiliary-ports.namespace2.namenode7</name>
  <value>8027,8028,8029</value>
  <description>
    Auxiliary ports for the NameNode to listen on. The value is a comma 
separated list of ports.
    In the case of HA/Federation where multiple namenodes exist,
    the name service id is added to the name e.g. ...
  </description>
</property>
{code}
I think we should support one interesting case, when 
{{dfs.namenode.rpc-address.auxiliary-ports = 0,0,0}} meaning that NN should 
have three auxiliary listeners bound to random ports. This is important for 
testing.

> Add configurable additional RPC listener to NameNode
> ----------------------------------------------------
>
>                 Key: HDFS-13566
>                 URL: https://issues.apache.org/jira/browse/HDFS-13566
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: ipc
>            Reporter: Chen Liang
>            Assignee: Chen Liang
>            Priority: Major
>         Attachments: HDFS-13566.001.patch, HDFS-13566.002.patch, 
> HDFS-13566.003.patch
>
>
> This Jira aims to add the capability to NameNode to run additional 
> listener(s). Such that NameNode can be accessed from multiple ports. 
> Fundamentally, this Jira tries to extend ipc.Server to allow configured with 
> more listeners, binding to different ports, but sharing the same call queue 
> and the handlers. Useful when different clients are only allowed to access 
> certain different ports. Combined with HDFS-13547, this also allows different 
> ports to have different SASL security levels. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to