[
https://issues.apache.org/jira/browse/HDFS-11096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16103867#comment-16103867
]
Sean Mackrory commented on HDFS-11096:
--------------------------------------
Updating: it was a recent change that broke this, I've posted a patch to fix it
that's being reviewed / iterated on, and I've updated my rolling upgrade test
scripts to actually confirm via the Job History Server that the jobs themselves
were FINISHED and SUCCESSFUL.
I re-ran the test with an early patch and I was able to get a successful
rolling upgrade with 5-10 minute delays between each step. So the entire
rolling upgrade of a 9-node (6 worker-node) cluster was spread out over 4 hours
and I didn't encounter any other issues, EXCEPT: in my test workload, I had to
increase Terasort's output replication, because some job failures were
occasionally happening when a job wrote to a node that was about to be taken
down for upgrades. I fixed that and no other actual compatibility issues in
Hadoop were found. I'll push the fixes out to Github soon...
> 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
