[
https://issues.apache.org/jira/browse/HDFS-12990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16323392#comment-16323392
]
Tsz Wo Nicholas Sze commented on HDFS-12990:
--------------------------------------------
I agree that changing from 8020 to 9820 seems not a good idea. This is not the
disagreement here.
The question is: how are we going to fix it?
> No incompatible changes are allowed between 3.0.0 and 3.0.1. Dot releases
> only allow bug fixes.
You may not like the statement above but it is our compatibility policy. My
request is, either we follow the policy or we revise it.
Some more questions:
- What if someone is already using 3.0.0 and has changed all the scripts to
9820?
- Compared to 2.x, 3.0.0 has many incompatible changes. Are we going to have
other incompatible changes in the future minor and dot releases? What is the
criteria to decide which incompatible changes are allowed?
- I hate that we have prematurely released 3.0.0 and make 3.0.1 incompatible to
3.0.0. If the "bug" is that serious, why not fixing it in 4.0.0 and declare
3.x as dead?
- It seems obvious that no one has seriously tested it so that the problem is
not uncovered until now. Are there bugs in our current release procedure?
> 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
