hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Yang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-12990) Change default NameNode RPC port back to 8020
Date Fri, 12 Jan 2018 02:41:00 GMT

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

Eric Yang commented on HDFS-12990:
----------------------------------

[~chris.douglas] I don't think the upgrade statement is true.  Hadoop cluster depends on implicit
default configuration to work is single node cluster.  Unless user did not define {{fs.default.name}}
nor {{dfs.namenode.rpc-address.mycluster.nn*}}, otherwise, default port number change make
no difference to upgrade.

Can we retract Hadoop 3.0.0 release and restore NN port to 8020 that we made a bad release?
 Can this be an alternate approach to produce Hadoop 3.0.1?

This is a good lesson to avoid time driven release for major version change.

> Change default NameNode RPC port back to 8020
> ---------------------------------------------
>
>                 Key: HDFS-12990
>                 URL: https://issues.apache.org/jira/browse/HDFS-12990
>             Project: Hadoop HDFS
>          Issue Type: Task
>          Components: namenode
>    Affects Versions: 3.0.0
>            Reporter: Xiao Chen
>            Assignee: Xiao Chen
>            Priority: Critical
>         Attachments: HDFS-12990.01.patch
>
>
> In HDFS-9427 (HDFS should not default to ephemeral ports), we changed all default ports
to ephemeral ports, which is very appreciated by admin. As part of that change, we also modified
the NN RPC port from the famous 8020 to 9820, to be closer to other ports changed there.
> With more integration going on, it appears that all the other ephemeral port changes
are fine, but the NN RPC port change is painful for downstream on migrating to Hadoop 3. Some
examples include:
> # Hive table locations pointing to hdfs://nn:port/dir
> # Downstream minicluster unit tests that assumed 8020
> # Oozie workflows / downstream scripts that used 8020
> This isn't a problem for HA URLs, since that does not include the port number. But considering
the downstream impact, instead of requiring all of them change their stuff, it would be a
way better experience to leave the NN port unchanged. This will benefit Hadoop 3 adoption
and ease unnecessary upgrade burdens.
> It is of course incompatible, but giving 3.0.0 is just out, IMO it worths to switch the
port back.



--
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


Mime
View raw message