[
https://issues.apache.org/jira/browse/HDFS-10391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16166581#comment-16166581
]
Daryn Sharp commented on HDFS-10391:
------------------------------------
-1. It's completely unnecessary for this to be incompatible, plus it's overly
complex for what it does and includes comments essentially saying "this isn't
correct". Why wasn't the default in the conf simply changed so that I can
change it back if I don't want the service port?
This release note states:
bq. The NameNode service RPC port is enabled by default
It should be: "A separate NameNode service RPC port is mandatory".
bq. The NameNode should always be setup with a service RPC port so that it
does not have to be explicitly enabled by an administrator.
We don't need to hold the hand of an admin while forcibly removing the option
to use a single port.
> Always enable NameNode service RPC port
> ---------------------------------------
>
> Key: HDFS-10391
> URL: https://issues.apache.org/jira/browse/HDFS-10391
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: datanode, namenode
> Reporter: Arpit Agarwal
> Assignee: Gergely Novák
> Labels: Incompatible
> Fix For: 3.0.0-beta1
>
> Attachments: HDFS-10391.001.patch, HDFS-10391.002.patch,
> HDFS-10391.003.patch, HDFS-10391.004.patch, HDFS-10391.005.patch,
> HDFS-10391.006.patch, HDFS-10391.007.patch, HDFS-10391.008.patch,
> HDFS-10391.009.patch, HDFS-10391.010.patch, HDFS-10391.v5-v6-delta.patch
>
>
> The NameNode should always be setup with a service RPC port so that it does
> not have to be explicitly enabled by an administrator.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
