Return-Path: 
 <user-return-8089-apmail-hadoop-common-user-archive=hadoop.apache.org@hadoop.apache.org>
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 B4EB6D2E4
	for <apmail-hadoop-common-user-archive@www.apache.org>;
 Wed, 22 May 2013 00:20:24 +0000 (UTC)
Received: (qmail 14750 invoked by uid 500); 22 May 2013 00:20:20 -0000
Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org
Received: (qmail 14643 invoked by uid 500); 22 May 2013 00:20:20 -0000
Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@hadoop.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@hadoop.apache.org>
List-Post: <mailto:user@hadoop.apache.org>
List-Id: <user.hadoop.apache.org>
Reply-To: user@hadoop.apache.org
Delivered-To: mailing list user@hadoop.apache.org
Received: (qmail 14636 invoked by uid 99); 22 May 2013 00:20:20 -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 00:20:20 +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 hadoop.ca@gmail.com designates
 209.85.128.50 as permitted sender)
Received: from [209.85.128.50] (HELO mail-qe0-f50.google.com) (209.85.128.50)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 May 2013 00:20:13 +0000
Received: by mail-qe0-f50.google.com with SMTP id x7so798678qeu.37
        for <user@hadoop.apache.org>; Tue, 21 May 2013 17:19:53 -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=LLLblZp2vGbI3SVtDX5U0Wzxvx46VEHhGnlpKOvTLG0=;
        b=kviSrMnGJIHpCQO1/8HLKOIgHElidWSRGOBxbfouHIIC3fIZUxXv9rPif3nV9GSqM+
         HrMUYq2h94kvR/iYdoQThZtk8sgPl8Dp9Z1p2D6kwl2W8zIYH/fBVMowXewlrUEgHE05
         NyCFDdJQ6G1MbXEP5N5N+0f4kcOF3wo2257qH/xoYnJVf5rWjgOdBOgUOR2GZDZDVP1w
         K+V/jqHjmFk2s8+usBYSVzqpAJzOYxFZyF8Wls8bIpl5o8hQYarnv1EThdQZ3XGZQAkB
         bxRm+aSCHMCyJsgHXfW7zmMUh9KaTpz/UA66MTP/rocf/bsZvBFmArD+8t1ALZPVsEqG
         pYEw==
MIME-Version: 1.0
X-Received: by 10.224.128.135 with SMTP id k7mr4817805qas.17.1369181993130;
 Tue, 21 May 2013 17:19:53 -0700 (PDT)
Received: by 10.49.95.37 with HTTP; Tue, 21 May 2013 17:19:53 -0700 (PDT)
Date: Tue, 21 May 2013 17:19:53 -0700
Message-ID: 
 <CALB5Fy-B6i8Px56WJHUPP=qWBMyE4RMwE3y3hRZJJXcgMURt1Q@mail.gmail.com>
Subject: upgrade from primary + secondary NN to active + standby NN
From: Serge Blazhievsky <hadoop.ca@gmail.com>
To: user@hadoop.apache.org
Content-Type: multipart/alternative; boundary=001a1132ece0557cc004dd4386d7
X-Virus-Checked: Checked by ClamAV on apache.org

--001a1132ece0557cc004dd4386d7
Content-Type: text/plain; charset=ISO-8859-1

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

--001a1132ece0557cc004dd4386d7
Content-Type: text/html; charset=ISO-8859-1

<div dir="ltr"><div><div><div><div>Hi guys,<br><br></div>I am planning to upgrade to HA architecture and I am not sure if metadata is backward capable. <br><br></div>Are there any problems that anybody is aware of?<br><br>
</div>Thanks in advance. <br></div>Serge <br></div>

--001a1132ece0557cc004dd4386d7--