[
https://issues.apache.org/jira/browse/HDFS-13566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16573443#comment-16573443
]
Erik Krogen commented on HDFS-13566:
------------------------------------
Cool, thanks for clarifying. My initial reaction to (3) was that it would be
too cumbersome for clients, but I can see some ways to set up configs to make
it easy to use:
* Set up a separate namespace in the configs, {{namespace2-aux}}, which points
to {{namespace2}} except using the auxiliary ports. Clients can specify
{{hdfs://namespace2}} for the standard port and {{namespace2-aux}} for
auxiliary.
* For configs located within DC2 (where {{namespace2}} is located), set up
{{namespace2}} with the standard port; for configs located in DC1, set up
{{namespace2}} with the auxiliary port.
I still wonder if it would be a reasonable addition to have something like
{{dfs.namenode.rpc-address.namespace2.use-aux}} to have a single config to
change for a client, but I think it is not necessary.
> 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]
