hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ray Chiang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-11096) Support rolling upgrade between 2.x and 3.x
Date Wed, 06 Sep 2017 22:05:00 GMT

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

Ray Chiang commented on HDFS-11096:

I'm trying out the patch now, and I have a few early comments:

# Setup
## It would be good to document the order of running the scripts (e.g. env.sh, call one of
the *_cluster_env() functions then build-distributed-hadoop).
## Add help documentation or document calling build-distributed-hadoop args.
## For trunk, it looks like V3 should now be 3.1.0-SNAPSHOT, not beta1.  We'll need to have
a branch-3.0
   version of the values.
# With the basic build-distribute-hadoop script
## It sources bash/functions.sh, which isn't visible if you're not running in dev-support/compat.
## It does a full checkout of the hadoop Git tree.  Since this does exist in the hadoop tree,
it might be good to support three modes (install from tarball, build and install from existing
tree, start up from fresh tree).
## Add parameter checking to build-distribute-hadoop so that VERSION (first arg) is required.
## Add checking to make sure one of the *_cluster_env() functions have been called before
running the bulk
   of the script

> 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

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

View raw message