[
https://issues.apache.org/jira/browse/HDFS-11096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16080837#comment-16080837
]
Ray Chiang commented on HDFS-11096:
-----------------------------------
Thanks for keeping this rolling [~mackrorysd] (no pun intended).
I was just thinking on this subject this morning and one thing occurred to me.
Do we have the capability to freeze the rolling upgrade process? If we can set
up combinations like:
* 25% old/75% new
* 50% old/50% new
* 75% old/25% new
while jobs continue to run, we could probably speed up some of the error
finding process.
Or maybe there's a better approach that would give similar results?
> 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: Lei (Eddy) Xu
> 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.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
