[
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.002.patch
Attaching a patch with a bunch of improvements:
* Addresses most (but not yet all) of the shellcheck warnings
* Uses www-us.apache.org to download released tarballs for Zookeeper and Hadoop
instead of more specific ones. Not sure if there's a better URL to use... I'm
also still using Github to check out trunk source as I had had issues using the
official repo - I assume that's not entirely Kosher...
* Fixed it so in Docker deployments, tarballs are built on persistent storage
to speed up future tests on the same host.
* Some refactoring of the pull-over-http-test as a step toward having more
WebHDFS compatibility tests going both ways. Had some issues connecting to
WebHDFS using the ns2 logical name, though. But what is currently in the patch
all works.
> 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, HDFS-11096.002.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]
