You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Andrew Wang (JIRA)" <ji...@apache.org> on 2017/01/04 19:01:01 UTC
[jira] [Commented] (HDFS-11096) Support rolling upgrade between 2.x
and 3.x
[ https://issues.apache.org/jira/browse/HDFS-11096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15799057#comment-15799057 ]
Andrew Wang commented on HDFS-11096:
------------------------------------
Thanks for the very thorough analysis here Sean! Do you think we should act on any of these changes? If so we can chase them in some other JIRAs.
Also, do you have any ideas on how we can whitelist items in the JACC report? Otherwise it's hard to see what's changing from report to report.
> 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: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org