[
https://issues.apache.org/jira/browse/HDFS-12990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16313820#comment-16313820
]
Anu Engineer commented on HDFS-12990:
-------------------------------------
bq. This includes the actual metadata location in hive tables, oozie workflows,
and more of the scripts than I could imagine.
Makes sense, I hated it when I had to maintain 2 sets of scripts for the 2.x
and 3.0 workflow.
bq. Anu Engineer - what are your thoughts? From a pragmatic standpoint, I think
this is definitely the right trade-off to make.
[~atm] I agree with you. However, I am sure someone(not me, I am +1 on this
change) will ask us why can the user change this default while deploying the
cluster if they need? Shouldn't it be easy to make this change in Ambari or
Cloudera Manager? Wearing my Apache Hat, I think this makes the life easy for
many customers who deploy apache bits without the use of these tools.
As a side note: I am also little ashamed that I am voting to break the
compatibility guidelines that I voted a +1 on very recently. Eating crow is a
fact of is life, I guess :(
> 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]
