[
https://issues.apache.org/jira/browse/HDFS-12990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16314252#comment-16314252
]
Xiao Chen edited comment on HDFS-12990 at 1/6/18 1:09 AM:
----------------------------------------------------------
Thanks [~anu] for understanding and agreeing on this.
Although there are tools like Ambari and CM, they cannot take care of all the
database changes like HMS, and the various downstream scripts out there. So
with both hats, I think this is the more user-friendly thing to do. :)
I have re-triggered the (mysteriously missing) pre-commit, and added release
notes for this. Feel free to edit the release notes if necessary. Will leave
this until mid of next week, to allow further comments.
was (Author: xiaochen):
Thanks [~anu] for understanding and agreeing on this.
Although there are tools like Ambari and CM, they cannot take care of all the
database changes like HMS, and the various downstream scripts out there. So
with both hats, I think this is the more user-friendly thing to do. :)
I have re-triggered the (mysteriously missing) pre-commit, and added release
notes for this. Feel free to edit the release notes if necessary.
> 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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
