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 67829D715 for ; Wed, 22 May 2013 04:56:12 +0000 (UTC) Received: (qmail 98845 invoked by uid 500); 22 May 2013 04:56:08 -0000 Delivered-To: apmail-hadoop-mapreduce-user-archive@hadoop.apache.org Received: (qmail 98706 invoked by uid 500); 22 May 2013 04:56:06 -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 98684 invoked by uid 99); 22 May 2013 04:56:06 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 May 2013 04:56:06 +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 (nike.apache.org: domain of harsh@cloudera.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; Wed, 22 May 2013 04:55:59 +0000 Received: by mail-ie0-f170.google.com with SMTP id aq17so4311743iec.1 for ; Tue, 21 May 2013 21:55:38 -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:from:date:message-id:subject:to :content-type:x-gm-message-state; bh=GslEvZg7I1ts7hr4gRcFjygL96v5L3QJ7YirHoE9l/8=; b=YcXFqxX4KzLValP7JNPUc1JGEzTWKnn+8RZ1f4GSDqqoM7IjEKGXJrLs2XxZ1hP26o 2QlHOU384xifHi7Pr7Dc3XdB3BC6wMUeghITTM9ME1QxMAbdOqaWc1+tRt3OEmH+cTxE fdomD4HJ7RfHnteQWttdChDy7erEVOiSErnIZMtKAouZ9WM6y6s604DC6iABMbEGP03u FoJcjJP0QnSwcyaUOpCdaTHEIhmNzcqf0AIMmDtJ9SEOl+gLpj4XewLYwH9Tgzjdifve rNLFVmPi7e67PqWGNjIOoC9PnR4onerPn4XWKoM+wVuq56ig9EzoIfqznnWutDT0oNpF naCg== X-Received: by 10.50.70.71 with SMTP id k7mr9679391igu.68.1369198538562; Tue, 21 May 2013 21:55:38 -0700 (PDT) MIME-Version: 1.0 Received: by 10.50.33.39 with HTTP; Tue, 21 May 2013 21:55:18 -0700 (PDT) In-Reply-To: References: From: Harsh J Date: Wed, 22 May 2013 10:25:18 +0530 Message-ID: Subject: Re: upgrade from primary + secondary NN to active + standby NN To: "" Content-Type: multipart/alternative; boundary=047d7b3a989c85007004dd47603a X-Gm-Message-State: ALoCoQkYpAZlClHxgGAJ9jEih7BZCIHdi55COfvaVNPzBP1CL+9dOe5xMvDzpFsuy2xac0msFM0B X-Virus-Checked: Checked by ClamAV on apache.org --047d7b3a989c85007004dd47603a Content-Type: text/plain; charset=ISO-8859-1 FWIW, I've seen through a lot of upgrades from 1.x to 2.x and metadata issue's never been a part of it. You should be able to safely upgrade and then to configure HA. Note that you cannot directly upgrade into HA mode yet, you have to upgrade to a regular 1.x to 2.x, and then as a next step, enable HA. Rollbacks are supported as long as you haven't finalized the metadata upgrade. I hope this covers the "backward capable" metadata question. If not, please rephrase that point? On Wed, May 22, 2013 at 5:49 AM, Serge Blazhievsky wrote: > Hi guys, > > I am planning to upgrade to HA architecture and I am not sure if metadata > is backward capable. > > Are there any problems that anybody is aware of? > > Thanks in advance. > Serge > -- Harsh J --047d7b3a989c85007004dd47603a Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
FWIW, I've seen through a lot of upgrades from 1.x to = 2.x and metadata issue's never been a part of it. You should be able to= safely upgrade and then to configure HA. Note that you cannot directly upg= rade into HA mode yet, you have to upgrade to a regular 1.x to 2.x, and the= n as a next step, enable HA.

Rollbacks are supported as long as you haven't fin= alized the metadata upgrade. I hope this covers the "backward capable&= quot; metadata question. If not, please rephrase that point?


On Wed, May 2= 2, 2013 at 5:49 AM, Serge Blazhievsky <hadoop.ca@gmail.com> wrote:
Hi guys= ,

I am planning to upgrade to HA architecture and I am not sur= e if metadata is backward capable.

Are there any problems that anybody is aware of?

Thanks in advance.
Serge



--
Harsh J
--047d7b3a989c85007004dd47603a--