hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantin Shvachko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-13566) Add configurable additional RPC listener to NameNode
Date Tue, 07 Aug 2018 23:31:00 GMT

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

Konstantin Shvachko commented on HDFS-13566:

Good question [~xkrogen]. Clients have few options:
# {{fs.defaultFS = hdfs://nn.company.com:8028}}
# Direct path: {{hadoop fs -ls  hdfs://nn.company.com:8028/path/to/file}}
# In federated and HA clusters the client config should specify {{dfs.namenode.rpc-address.namespace2.namenode7
= nn.company.com:8028}}.
We may verify on the client side that {{8028}} is a valid port by checking that it belongs
to {{auxiliary-ports}}. This should be the proxy provider logic.

So on the client side we need to specify explicitly which (auxiliary) port must be used. Particularly
in the context of encrypted connections we will use port 8028 if the client is outside of
the data center, and 8020 for the native data center clients. With port 8020 being closed
for outside connection.
Hope this makes sense.

> 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

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message