[
https://issues.apache.org/jira/browse/HDFS-11096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16080798#comment-16080798
]
Sean Mackrory commented on HDFS-11096:
--------------------------------------
For anyone following this thread, I've come back to this and pushed some
updates to the tests at https://github.com/mackrorysd/hadoop-compatibility.
* fixes for some idempotence / SSH automation problems that could've popped up
before in the rolling upgrade test, and actually validating the sorted data.
* [~eddyxu] wrote a little framework for writing tests against mini HDFS
clusters of 2 different versions in Python, and a test that you can cp between
2 clusters. I did a bit of refactoring and added tests that check for similar
output for most of the "hdfs dfs" commands currently in Hadoop 2.
> 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
