Sean Mackrory commented on HDFS-11096:

Just pushed some more updates. HDFS-12151 is fixed, and I'm once again able to 
do successful rolling upgrades, even with large delays during the upgrade. I 
made a quick attempt at doing a rolling upgrade of YARN, but the commands I 
thought one was supposed to use to stop / start daemons aren't working. The 
script is there, just not currently called from rolling-upgrade.sh. Not sure if 
you want to work off of that for YARN's side of things [~rchiang]?

I'm also working on adding Docker support and hopefully using the same Docker 
images we use for precommit jobs, etc. to make the build environment easier to 
put in place and make this more easily verifiable by others.

> 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
> 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

To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

Reply via email to