You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Arpit Agarwal (JIRA)" <ji...@apache.org> on 2017/08/01 20:20:00 UTC
[jira] [Commented] (HDFS-10391) Always enable NameNode service RPC
port
[ https://issues.apache.org/jira/browse/HDFS-10391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16109680#comment-16109680 ]
Arpit Agarwal commented on HDFS-10391:
--------------------------------------
Hi [~xyao],
I tried making these two changes and hit a bunch of unit test failures.
bq. Line 433-463 (original NamenodeRPCServer.java): should we remove the service related RPCs from the client RPC server as we are not allow fallback
bq. Line 343-345: should we ensure only the service RPCs are added/set here?
I think the broken tests need to be updated. Is it okay if we address these two remaining ideas in a follow up Jira?
> 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
> 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.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: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org