[
https://issues.apache.org/jira/browse/HDFS-11096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16186201#comment-16186201
]
Aaron T. Myers commented on HDFS-11096:
---------------------------------------
bq. Currently YARN rolling upgrades are actually failing because the Hadoop 3
ResourceManager is using URIs like http://ns1:8020/... (logical namespace name
used as though it's a hostname). Not sure where that's coming from yet, I need
to dig there, but I doubt the fix there will invalidate much review of the
current code.
I investigated this the other day and came to the conclusion that this is due
to a bug introduced by YARN-6457. See [this
comment|https://issues.apache.org/jira/browse/YARN-6457?focusedCommentId=16184700&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16184700]
in particular for a description of the issue.
> Support rolling upgrade between 2.x and 3.x
> -------------------------------------------
>
> Key: HDFS-11096
> URL: https://issues.apache.org/jira/browse/HDFS-11096
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: rolling upgrades
> Affects Versions: 3.0.0-alpha1
> Reporter: Andrew Wang
> Assignee: Sean Mackrory
> Priority: Blocker
> Attachments: HDFS-11096.001.patch, HDFS-11096.002.patch,
> HDFS-11096.003.patch, HDFS-11096.004.patch
>
>
> trunk has a minimum software version of 3.0.0-alpha1. This means we can't
> rolling upgrade between branch-2 and trunk.
> This is a showstopper for large deployments. Unless there are very compelling
> reasons to break compatibility, let's restore the ability to rolling upgrade
> to 3.x releases.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
