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

Owen O'Malley commented on HDFS-12990:
--------------------------------------

Ok, I'm late on this.

I'm strongly on the side of changing it back. In my view, this should 
absolutely be a blocker bug on any release. We *need* to change the port back 
because it is part of the public API.

As always, you need to view the relative costs:
 # Users who have installed 3.0.0 and will be inconvenienced by the change.
 # All other users of Hadoop.

Clearly bucket number 2 is much much larger than 1.

Let's also be clear that the release manager can put it in or out of the RC as 
they deem fit. There are NO vetoes. It is a straight vote for whether the RC 
should be released. Personally, I'll vote against an RC that doesn't have this 
patch.

> 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
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

Reply via email to