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 9055110324 for ; Fri, 30 May 2014 13:44:32 +0000 (UTC) Received: (qmail 56185 invoked by uid 500); 30 May 2014 13:44:28 -0000 Delivered-To: apmail-hadoop-user-archive@hadoop.apache.org Received: (qmail 56071 invoked by uid 500); 30 May 2014 13:44:28 -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 56064 invoked by uid 99); 30 May 2014 13:44:28 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 May 2014 13:44:28 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [212.227.17.24] (HELO mout.kundenserver.de) (212.227.17.24) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 May 2014 13:44:24 +0000 Received: from localhost.localdomain (host-92-19-252-226.static.as13285.net [92.19.252.226]) by mrelayeu.kundenserver.de (node=mreue102) with ESMTP (Nemesis) id 0Lgpny-1WVwJi3THy-00oEky; Fri, 30 May 2014 15:44:01 +0200 From: Ian Brooks To: user@hadoop.apache.org Subject: Re: Upgrade to 2.4 Date: Fri, 30 May 2014 14:43:59 +0100 Message-ID: <17520513.usH1rV0ftE@localhost.localdomain> User-Agent: KMail/4.12.5 (Linux/3.14.4-200.fc20.x86_64; KDE/4.12.5; x86_64; ; ) In-Reply-To: References: <12627914.21J6Illjg6@localhost.localdomain> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Provags-ID: V02:K0:TrXPfL6HQuZv0m41/Z0saVN0TQ7ydeRxQ/0JAC8hK3i 0zoIYCov6Nb42Tcmpjo5Zavcf2uEB9YAIvaaz01JyABBJS355r jBKDA1R5mvFflaOFFXZ59wXx5DPnTScxFxx7TBVgE4zD2QU6Id 8mUC+5qHbElFJ7/53zgBA7R7pzPsubNS8Cm2qkchKjFwZ9n5ZH Hq+wmOeBbfCYAHPDqYm+mTkrFUZ7YOdCLKgz7vpijd31DyzSg+ ZbquMSIpMl1ekc8e7ZdMxdZ8A8mFMg/sxCQp1BgFg45XzzGT2l /37Y1I8r9h/A9nb5eM4VCchsehCyb5YCu2MtUDzrt6sbJ+iU1z L4SjvaIMtZJ6kkAEKtXZQoftOy235O+HBLI7K2E6E97g1vQTud J+5hcB10yGlpA== X-Virus-Checked: Checked by ClamAV on apache.org Thanks, Ill give it a try. -Ian On Friday 30 May 2014 19:43:00 Zesheng Wu wrote: > Hi Ian, > -rollingUpgrade is available since hadoop 2.4, so you can't use > -rollingUpgrade to upgrade a 2.3 cluster to 2.4. > Because HDFS 2.4 introduce protobuf formated fsimage, we must stop the > whole cluster and then upgrade the cluster. > I tried to upgrade a 2.0 HDFS cluster to 2.4 several days ago, following > are some details, wish this can give some help to you: > > 1. Put the active NN into safemode: dfsadmin -safemode enter > 2. Perform a saveNamespace operation: dfsadmin -saveNamespace > 3. For each component you are using, back up configuration data, databases, > and other important files > 4. Shutdown hadoop serverice across your entire cluster > 5. Check each host to make sure that there are no processes running > hdfs/yarn > 6. Back up your HDFS metadata > 7. Upgrade and start the Journal Nodes and ZKFC > 8. Make sure that all the journal nodes and zkfc have started normally > 9. Execute this upgrade operation on active NN: namenode -upgrade > (Important) > 10. Wait and make sure from ANN's log that upgrade is completed (from log) > 11. Bootstrap standby NN: namenode -bootstrapStandby > 12. Start standby NN: namenode start > 13. Start each of the DNs: datanode start > 14. Make sure that everything is running smoothly, this could take a matter > of days, or even weeks > 15. Finalize the hdfs metadata upgrade: dfsadmin -finalizeUpgrade > > > 2014-05-30 17:54 GMT+08:00 Ian Brooks : > > > Hi, > > > > I though i'd give hadoop 2.4 a try as the improvements to rolling upgrades > > would be useful to us. Unless i'm missing something, I can't see how to > > upgrade from 2.3 to 2.4 > > > > -rollingUpgrade doesnt work as the old namenode doesn't understand the > > command and -upgrade is no longer available. > > > > I had a quick google and can't find any documentation on this upgrade, > > does anyone know how its supposed to be done? > > > > -Ian > > > > > > -- -Ian Brooks Senior server administrator - Sensewhere