Return-Path: X-Original-To: apmail-hadoop-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-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 A2D8F10023 for ; Thu, 14 Nov 2013 08:40:13 +0000 (UTC) Received: (qmail 47870 invoked by uid 500); 14 Nov 2013 08:39:57 -0000 Delivered-To: apmail-hadoop-user-archive@hadoop.apache.org Received: (qmail 47642 invoked by uid 500); 14 Nov 2013 08:39:53 -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 47625 invoked by uid 99); 14 Nov 2013 08:39:51 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Nov 2013 08:39:51 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of yypvsxf19870706@gmail.com designates 209.85.216.174 as permitted sender) Received: from [209.85.216.174] (HELO mail-qc0-f174.google.com) (209.85.216.174) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Nov 2013 08:39:46 +0000 Received: by mail-qc0-f174.google.com with SMTP id v2so957073qcr.5 for ; Thu, 14 Nov 2013 00:39:25 -0800 (PST) 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=ZAHKWK2PDkIUiumj+NBDgeVhZcOCeupqQLHC2a1Z+Po=; b=Ay56tosw95XKXozie+4LyYCThDz8n7i1lCou4XXIjuez0ViTeqiq9SefPR0Qp9veLT PYDHKXe3Xqrv25xvRLK6VHAtWwKSz0HDZh/9e3d9V7zEDV8iXn8lGC/xnHv8kBnGLcux cc+r5RlT/e8Z0Ztl92muDBpo2eC9GFjGkklNjl7a2JoOyfCv+Z56xfNWngS8n/l4I6Qs vn5qf/YWXsTfDqFz6epaFHeASfdwurf5N+aHla5yUTpw55Nphs6zTa+iFBh//IAaGE6p vXRfOhNT9ofif8pFkQkWmyRd+Tihp98eh9JcLlsCTcoHwrmp6VtEHTogDBjJJsaxf8iN ZRUQ== MIME-Version: 1.0 X-Received: by 10.224.29.67 with SMTP id p3mr445349qac.30.1384418365562; Thu, 14 Nov 2013 00:39:25 -0800 (PST) Received: by 10.96.145.232 with HTTP; Thu, 14 Nov 2013 00:39:25 -0800 (PST) Date: Thu, 14 Nov 2013 16:39:25 +0800 Message-ID: Subject: Upgrade with HA enabled From: YouPeng Yang To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=047d7bdca560e6640504eb1f0409 X-Virus-Checked: Checked by ClamAV on apache.org --047d7bdca560e6640504eb1f0409 Content-Type: text/plain; charset=ISO-8859-1 Hi I am doing the upgrade test from 2.0.5.alpha to 2.2.0. On the original 2.0.5.alpha ,I have enable the HA,and when I do the upgrade ,It comes out an exception[1]: So what's is step to upgrade with HA enabled.Do I need to disable the HA,and do the upgrade on the namenode and the backupnode seperately. Hmm,Is there possiblity to upgrade with the HA enabled? Regard [1]---------------------------------------------------------------------------------------------------------------- 13/11/14 16:28:38 INFO namenode.NameNode: registered UNIX signal handlers for [TERM, HUP, INT] 13/11/14 16:28:39 FATAL namenode.NameNode: Exception in namenode join org.apache.hadoop.HadoopIllegalArgumentException: Invalid startup option. Cannot perform DFS upgrade with HA enabled. at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1207) at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1320) 13/11/14 16:28:39 INFO util.ExitUtil: Exiting with status 1 13/11/14 16:28:39 INFO namenode.NameNode: SHUTDOWN_MSG: ---------------------------------------------------------------------------------------------------------------- --047d7bdca560e6640504eb1f0409 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi
=A0 I am doing the upgrade test= from 2.0.5.alpha to 2.2.0.
=A0 On the original 2.0.5.alpha ,I hav= e enable the HA,and when I do the upgrade ,It comes out an exception[1]:
=A0 So what's is step to upgrade with HA enabled.Do I need to disable t= he HA,and do the upgrade on the namenode and the backupnode seperately. Hmm= ,Is there
possiblity to upgrade with the HA enabled?


Regard






[= 1]-------------------------------------------------------------------------= ---------------------------------------
13/11/14 16:28:38 INFO namenode.= NameNode: registered UNIX signal handlers for [TERM, HUP, INT]
13/11/14 16:28:39 FATAL namenode.NameNode: Exception in namenode join
or= g.apache.hadoop.HadoopIllegalArgumentException: Invalid startup option. Can= not perform DFS upgrade with HA enabled.
=A0=A0=A0 at org.apache.hadoop.= hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1207)
=A0=A0=A0 at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.= java:1320)
13/11/14 16:28:39 INFO util.ExitUtil: Exiting with status 113/11/14 16:28:39 INFO namenode.NameNode: SHUTDOWN_MSG:
-------------= ---------------------------------------------------------------------------= ------------------------
--047d7bdca560e6640504eb1f0409--