Anu Engineer commented on HDFS-12990:

I agree with [~atm] (based on comments in the mailing list) that we have 
discussed this issue in depth, 
 both in this JIRA and in the mailing lists. As 3.0.1 is going to vote on Feb 
9th, this is the last window 
 for us to commit or discard this JIRA.

To break this impasse, I would like to propose that we commit this patch on Feb 
6th, Noon, PST. 
 If anyone in the community feels that this should not be committed, +*Please 
provide your -1*+;
 If we don't see an explicit -1, +I will commit this patch on Feb 6th, Tuesday, 
Noon, Pacific Standard Time+. 
 I am hoping this will allow us to get to vote on 3.0.1.

I would like to propose further that we as a community tag 3.0.0 as *abandoned* 
so that we don't 
 have to live with RPC port change in one version.

[~eyang], I know you have indicated that you are a -1 on this patch, but then 
later proposed we discuss this. 
 *If you are still a -1 on this change, could you please make it explicit?*

[~atm], [~eddyxu], [~xiaochen] Please let me know if you see any issues with 
this late commit and 
 rolling the release; I prefer this Jira to be resolved before we get to vote.

> 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

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