[
https://issues.apache.org/jira/browse/HDFS-11096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15816623#comment-15816623
]
Andrew Wang commented on HDFS-11096:
------------------------------------
Thanks for checking all this Sean, a couple replies:
* Nice find on HDFS-11312, particularly since it's also an issue in branch-2.8.
* Not sure on the string -> type conversion, but it's in branch-2.8 so it does
need confirmation real soon. I don't see a compatibility discussion on
YARN-3583 where this was done.
* The discussion on YARN-4844 explains that int32 and int64 are both just
varints under the hood, so upgrading is okay except for the overflow issue.
Since the point of upgrading the types is to fix overflow, this seems okay to
me.
* Moving messages between files seems fine to me, as long we also updated
references to point to the new locations.
> 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
> Priority: Blocker
>
> 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.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
