[ 
https://issues.apache.org/jira/browse/HDFS-2983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13248716#comment-13248716
 ] 

Todd Lipcon commented on HDFS-2983:
-----------------------------------

Hey Sanjay. I agree that the snapshot-on-upgrade feature is really important, 
and I don't think this work precludes/breaks that. Here's my line of thinking:
- even with the ability to do rolling upgrade, there is no restriction that you 
_must_ do upgrades like this. So, you could still decide to use the current 
upgrade process as a policy decision.
- As you mentioned, many upgrades/hotfixes/EBFs don't touch core code, so for 
those, most people would prefer a rolling upgrade without downtime.
- separately, after this is committed, we can work on figuring out a strategy 
that allows you to do an upgrade-style snapshot before starting the rolling 
upgrade. It looks like you just filed HDFS-3225 for this, so let's continue 
this discussion there.

Agree?
                
> Relax the build version check to permit rolling upgrades within a release
> -------------------------------------------------------------------------
>
>                 Key: HDFS-2983
>                 URL: https://issues.apache.org/jira/browse/HDFS-2983
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>    Affects Versions: 2.0.0
>            Reporter: Eli Collins
>            Assignee: Aaron T. Myers
>         Attachments: HDFS-2983.patch
>
>
> Currently the version check for DN/NN communication is strict (it checks the 
> exact svn revision or git hash, Storage#getBuildVersion calls 
> VersionInfo#getRevision), which prevents rolling upgrades across any 
> releases. Once we have the PB-base RPC in place (coming soon to branch-23) 
> we'll have the necessary pieces in place to loosen this restriction, though 
> perhaps it takes another 23 minor release or so before we're ready to commit 
> to making the minor versions compatible.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to