Eric Yang commented on HDFS-12990:

[~anu] It's not clear to determine this patch would cause people more time to 
handle the exception case for 3.0.0 port uniqueness or more time to spend on 
upgrading cluster without port in namenode URL.  The answer might be changing 
over time.  This value can be customized to prevent backward compatible 
breakage in most cases.  Since there is no data to backup which way will save 
people time for the next 3 years, this change is not a good use of veto power.  
As the result, I agree this is not an incompatible change between 3.0.0 and 
3.0.1 because 3.0.0 documentation explicit stated to include port number for 
fs.defaultFS .  I retract my -1 vote, and provide -0 vote on this 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

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