Return-Path: X-Original-To: apmail-hadoop-common-user-archive@www.apache.org Delivered-To: apmail-hadoop-common-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E41A510125 for ; Fri, 21 Jun 2013 07:17:27 +0000 (UTC) Received: (qmail 71710 invoked by uid 500); 21 Jun 2013 07:17:18 -0000 Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org Received: (qmail 71625 invoked by uid 500); 21 Jun 2013 07:17:07 -0000 Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hadoop.apache.org Delivered-To: mailing list user@hadoop.apache.org Received: (qmail 71611 invoked by uid 99); 21 Jun 2013 07:17:05 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Jun 2013 07:17:05 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of azuryyyu@gmail.com designates 209.85.223.170 as permitted sender) Received: from [209.85.223.170] (HELO mail-ie0-f170.google.com) (209.85.223.170) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Jun 2013 07:17:01 +0000 Received: by mail-ie0-f170.google.com with SMTP id e11so19161937iej.29 for ; Fri, 21 Jun 2013 00:16:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=8TYXe9yiybHqo5t1vhalT8+DTrijQbtWMIim6dd2+3E=; b=VufHfLzpoPwBS2JFs+m/ZaA2lsE8qq7KnHolmYDs/MsOu21YwwvMAHmRdglHMoXHJB 2jcE0RB+9e8McxdY0Lo4xQiWY5+/oKMpbbYMc5l5zSEsh1zldfcq1HKLhSrNiM3QhR6p H1mwxVH8evunyzh1hzSipokO0HkEKTRA/+IibyfeaJlIKxlMklJUs7EajJfghH53uHTM ioq1RLH/3T7URfFtKGnEuZRGpxg82ynpQx3wUvgV8O3GVoSxAhdUkZ+olyq/6fpKQj4P P8D4ZX7G9dp2Q15+g70IFHsBRemTjVqSob77E4NOA7npmVPgBrh4XJ1lh2JAQ4VtY8nQ HyQg== MIME-Version: 1.0 X-Received: by 10.50.77.80 with SMTP id q16mr1584701igw.3.1371799000550; Fri, 21 Jun 2013 00:16:40 -0700 (PDT) Received: by 10.64.61.67 with HTTP; Fri, 21 Jun 2013 00:16:40 -0700 (PDT) Date: Fri, 21 Jun 2013 15:16:40 +0800 Message-ID: Subject: HDFS upgrade under HA From: Azuryy Yu To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=047d7bdc123821df2804dfa4d815 X-Virus-Checked: Checked by ClamAV on apache.org --047d7bdc123821df2804dfa4d815 Content-Type: text/plain; charset=ISO-8859-1 Hi, The layout version is -43 until 2.0.4-alpha, but HDFS-4908 changed layout version to -45. so if My test cluster is running hadoop-2.0.4-alpha(-43), which is upgraded from hadoop-1.0.4, then I want to upgrade using trunk(-45), how to do? It cannot upgrade under HA, so I can use hadoop-1.0.4 core-site and hdfs-site, then "start-dfs.sh -upgrade", but standby NN cannot upgrade, so how to upgrade standby NN under HA? --047d7bdc123821df2804dfa4d815 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi,

The layout version is= -43 until 2.0.4-alpha, but HDFS-4908 changed layout version to -45.
so if My test cluster is running hadoop-2.0.4-alpha(-43), which is = upgraded from hadoop-1.0.4, then I want to upgrade using trunk(-45), how to= do?

It cannot upgrade under HA, so I can use hadoop-1.0.4 core-site a= nd hdfs-site, then "start-dfs.sh -upgrade", but standby NN cannot= upgrade,

so how to upgrade standby NN under HA?

--047d7bdc123821df2804dfa4d815--