Return-Path: X-Original-To: apmail-hadoop-mapreduce-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-mapreduce-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 53466CECA for ; Fri, 21 Jun 2013 18:54:29 +0000 (UTC) Received: (qmail 92901 invoked by uid 500); 21 Jun 2013 18:54:24 -0000 Delivered-To: apmail-hadoop-mapreduce-user-archive@hadoop.apache.org Received: (qmail 92757 invoked by uid 500); 21 Jun 2013 18:54:24 -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 92750 invoked by uid 99); 21 Jun 2013 18:54:24 -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 18:54:24 +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 suresh@hortonworks.com designates 209.85.216.54 as permitted sender) Received: from [209.85.216.54] (HELO mail-qa0-f54.google.com) (209.85.216.54) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Jun 2013 18:54:19 +0000 Received: by mail-qa0-f54.google.com with SMTP id n20so821179qaj.20 for ; Fri, 21 Jun 2013 11:53:58 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=+QNadAoDAQsVFMrREM44rmT7JjmiwA3PLrbHUQVrJx4=; b=iMoYUvNL9AOUaEfvkkG5vtkYcDyFFW6NJhUUQcrgBXI2dWTWqga5cqPCehozPb/4wt 7UsSc94R5fSQtmBiVoB1gwGGD2Ri9uY7NgHVszvmTLEEzLJWk7WX2CmK5/4ZroA7MBbG d0Y9R/a1QIY9xJqJPJbtYwkPK/MW+yTgqXptdO+TLsijKLJnAUdhUNVPsWlLkE3Mk7wj pgy+UsYk/sqCQKvEm5l35Ukb4R0KQHZC4K2ytK71VCDUVwKqj1Y388gImpLDT2QNthQ5 ZSoCzHTCX1OAvaOnnh4VF4uHA7Yht4eahIk72xfLT3hOyXAmBP21L5m3x/Ujm9AUi/DF 52wQ== MIME-Version: 1.0 X-Received: by 10.49.71.38 with SMTP id r6mr9707190qeu.30.1371840838572; Fri, 21 Jun 2013 11:53:58 -0700 (PDT) Received: by 10.49.121.131 with HTTP; Fri, 21 Jun 2013 11:53:58 -0700 (PDT) In-Reply-To: References: Date: Fri, 21 Jun 2013 11:53:58 -0700 Message-ID: Subject: Re: HDFS upgrade under HA From: Suresh Srinivas To: "hdfs-user@hadoop.apache.org" Content-Type: multipart/alternative; boundary=047d7b5d8b5ddf489604dfae95a4 X-Gm-Message-State: ALoCoQlvAE2vTLxz6IaWusLToVD7fhYu6kQXHOqfmLLhjQw5S5UiUc3KKoXwBk7sCsSrBpYPy0l8 X-Virus-Checked: Checked by ClamAV on apache.org --047d7b5d8b5ddf489604dfae95a4 Content-Type: text/plain; charset=ISO-8859-1 I have hard time understanding your question. On Fri, Jun 21, 2013 at 12:16 AM, Azuryy Yu wrote: > 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? > Layout version can increase (or decrease given it is negative number) by more than 1, when you upgrade to a new release. So 2.0.4-alpha(-43) can upgrade to trunk(-45) version. > > 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, > What is preventing you from upgrading? Please add details on what you are doing and what issue you are seeing. Regards, Suresh --047d7b5d8b5ddf489604dfae95a4 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
I have hard time understanding your question.



On Fri, Jun= 21, 2013 at 12:16 AM, Azuryy Yu <azuryyyu@gmail.com> wrote= :
Hi,

The = layout version is -43 until 2.0.4-alpha, but HDFS-4908 changed layout versi= on to -45.

so if My test cluster is running hadoop-2.0.4-alpha(-43), which i= s upgraded from hadoop-1.0.4, then I want to upgrade using trunk(-45), how = to do?

Layout version= can increase (or decrease given it is negative number) by more than 1, whe= n you upgrade to a new release. So 2.0.4-alpha(-43) can upgrade to trunk(-4= 5) version.
=A0

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,

What is pr= eventing you from upgrading? Please add details on what you are doing and w= hat issue you are seeing.

Regards,
Suresh

--047d7b5d8b5ddf489604dfae95a4--