[ 
https://issues.apache.org/jira/browse/HDFS-11096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sean Mackrory updated HDFS-11096:
---------------------------------
    Attachment: HDFS-11096.001.patch

So Docker support has been added for the rolling-upgrade and pull-over-http 
test. They're using the same Docker image as Yetus builds, etc. And they've 
been really robust lately. I've corrected the copyright headers at the top of 
the files, and I think dev-support/compat is a good place for these tests to 
live - but I'm open to other ideas as well.

The Python tests are all still working, but they did not seem to catch the 
previous incompatibility that prevented older clients from writing to newer 
DataNodes. There's also still a few TODOs or thing that don't work and it's not 
clear why. So definitely more work to be done, but there's value in the 
existing CLI compatibility tests.

I'd like to get this put in the codebase and get some Jenkins jobs running on 
it 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: Sean Mackrory
>            Priority: Blocker
>         Attachments: HDFS-11096.001.patch
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to