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 "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2017/02/03 23:45:52 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=15852343#comment-15852343 ] 

Allen Wittenauer commented on HDFS-11096:
-----------------------------------------

I hope folks hoping to do a rolling upgrade with automated tools understand that hadoop-env.sh/yarn-env.sh, log files, pid files, and a few other things that are outside of the Java code were purposefully made incompatible and will do the correct thing when trying to roll forward....

> 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.15#6346)

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