[
https://issues.apache.org/jira/browse/HDFS-12990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16317507#comment-16317507
]
Aaron T. Myers commented on HDFS-12990:
---------------------------------------
bq. No incompatible changes are allowed between 3.0.0 and 3.0.1. Dot releases
only allow bug fixes. Won't you agree?
In general I agree that we should avoid making incompatible changes in dot or
minor releases, but I also believe that we have historically evaluated any
change like this on a case-by-case basis. I'm sure I can find some examples
where we have made incompatible changes in minor or dot releases because we
concluded that the benefits outweighed the costs. For example, I believe we
have upgraded a dependency to address a security issue.
Regardless, I'm happy to discuss this more broadly and see how others view the
compatibility guidelines in this respect. I'll start a thread on common-dev@ to
discuss this and we can go from there.
> 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: [email protected]
For additional commands, e-mail: [email protected]
