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 72A211063F for ; Wed, 25 Sep 2013 19:54:26 +0000 (UTC) Received: (qmail 40250 invoked by uid 500); 25 Sep 2013 19:54:19 -0000 Delivered-To: apmail-hadoop-user-archive@hadoop.apache.org Received: (qmail 40147 invoked by uid 500); 25 Sep 2013 19:54:19 -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 40140 invoked by uid 99); 25 Sep 2013 19:54:18 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Sep 2013 19:54:18 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy includes SPF record at spf.trusted-forwarder.org) Received: from [216.109.114.159] (HELO nm41-vm4.bullet.mail.bf1.yahoo.com) (216.109.114.159) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Sep 2013 19:54:12 +0000 Received: from [66.196.81.173] by nm41.bullet.mail.bf1.yahoo.com with NNFMP; 25 Sep 2013 19:53:51 -0000 Received: from [98.139.212.236] by tm19.bullet.mail.bf1.yahoo.com with NNFMP; 25 Sep 2013 19:53:51 -0000 Received: from [127.0.0.1] by omp1045.mail.bf1.yahoo.com with NNFMP; 25 Sep 2013 19:53:51 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 264867.74613.bm@omp1045.mail.bf1.yahoo.com Received: (qmail 94174 invoked by uid 60001); 25 Sep 2013 19:53:51 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ymail.com; s=s1024; t=1380138831; bh=qeF5qUn3pOGFxVr+MyqgWod+5sZFySDstJLL5mm4Bug=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=nhD8a0YWNM1XpqWMSoeRkCkqCaeYtYra8nDSG+uQ1uHtlXGD1du2IbJyTGmMLtd6X5o6Z6wcPijQo7KOjDAAQ3jg8Yk3XDsAhF3Is7NMH1nwamJ134y6JxNsxv8nf0sNsMrJssKga/DKrQ5unfgZFImlXj8gpRQaoPXo/Lk/52c= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=ymail.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=Zmw5ef2Oi4w8Wv1Q443RbxW4zlBI3T98Hs8ryrRfSEXPeh7GMn4zXBCC4TzOx8dPn5PQ545f2dWXpMiYcLLbAV21mZN2uvnszQXSEc93GopWCBw6OLOVQ5ciFe0uVnIs7yXkwqMD83o5Ok1Czv043HUgKs88VoVhYbVFqHSaBJc=; X-YMail-OSG: 4EmTPSkVM1nqr8Xh_4CmtQaRU9QheOgegSUxecEmayGX2Ui RjkKbPKArVwtdZ4SLxuhLt4yquUQghucOTCWng0kK3vhVSyWreWcPiSRH3_K SkLJyngWwnbzwqHZQP5bDD1kllhZigzrWGR0TwrrpJuiPz8uPwVV_YmKXA99 nIq4WuFMz.TFLgyP_6jficHzt06cJ5c8kXK5A0RjTq5ioDBiejhPgFyoSVjz 5Xquph2S1CJ6Ah_Lheg16X7e5nehfhzplT9BcptzHUxZ_6_ZZQtfYboQ1lEz S1DEB_t5gdNPEVvZf6Z9ipvQnrrmNwUm1RaGZZltiibhyeR.7qn5c6tIgQJy UK0SLFuSYVZhh1P9iplGjdTivi0vzw5OxZA83en6LIPAPfHGfu3vUK16aK0C Iypaqs5iBrjMj.0M.e1kWXdJ5nMlPs2qJmWI.CgCLPJm.IvDzxBym6Rd8nr3 efW5Ff7oNYBAgamOOebaQuKUdwxeJ2t4hbRl9afdXqxB7X7SzB.Sf1.Dumls dfMLwHdkfzscPukXflPDgT.wgdikz9x6qfFLp5Yy8g3uXyVP4 Received: from [98.228.48.177] by web141202.mail.bf1.yahoo.com via HTTP; Wed, 25 Sep 2013 12:53:50 PDT X-Rocket-MIMEInfo: 002.001,VG9tISBJIHdvdWxkIGd1ZXNzIHRoYXQganVzdCBnaXZpbmcgdGhlIE5OIEpWTSBsb3RzIG9mIG1lbW9yeSAoNjRHYiAvIDk2R2IpIHNob3VsZCBiZSB0aGUgZWFzaWVzdCB3YXkuCgoKCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwogRnJvbTogVG9tIEJyb3duIDx0b21icm93bjUyQGdtYWlsLmNvbT4KVG86ICJ1c2VyQGhhZG9vcC5hcGFjaGUub3JnIiA8dXNlckBoYWRvb3AuYXBhY2hlLm9yZz4gClNlbnQ6IFdlZG5lc2RheSwgU2VwdGVtYmVyIDI1LCAyMDEzIDExOjI5IEFNClN1YmplY3Q6IEkBMAEBAQE- X-Mailer: YahooMailWebService/0.8.157.561 References: Message-ID: <1380138830.85455.YahooMailNeo@web141202.mail.bf1.yahoo.com> Date: Wed, 25 Sep 2013 12:53:50 -0700 (PDT) From: Ravi Prakash Reply-To: Ravi Prakash Subject: Re: Is there any way to partially process HDFS edits? To: "user@hadoop.apache.org" In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="624387052-725184109-1380138830=:85455" X-Virus-Checked: Checked by ClamAV on apache.org --624387052-725184109-1380138830=:85455 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Tom! I would guess that just giving the NN JVM lots of memory (64Gb / 96Gb)= should be the easiest way.=0A=0A=0A=0A=0A________________________________= =0A From: Tom Brown =0ATo: "user@hadoop.apache.org" <= user@hadoop.apache.org> =0ASent: Wednesday, September 25, 2013 11:29 AM=0AS= ubject: Is there any way to partially process HDFS edits?=0A =0A=0A=0AI hav= e an edits file on my namenode that is 35GB. This is quite a bit larger tha= n it should be (the secondary namenode wasn't running for some time, and=A0= HBASE-9648 caused a huge number of additional edits).=0A=0AThe first time I= tried to start the namenode, it chewed on the edits for about 4 hours and = then ran out of memory. I have increased the memory available to the nameno= de (was 512MB, now 2GB), and started the process again.=0A=0AIs there any w= ay that the edits file can be partially processed to avoid having to re-pro= cess the same edits over and over until I can allocate enough memory for it= to be done in one shot?=0A=0A=0AHow long should it take (hours? days?) to = process an edits file of that size?=0A=0AAny help is appreciated!=0A=0A--To= m --624387052-725184109-1380138830=:85455 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable
Tom! I would guess th= at just giving the NN JVM lots of memory (64Gb / 96Gb) should be the easies= t way.



= From: Tom Brown <tombrown52= @gmail.com>
To: "us= er@hadoop.apache.org" <user@hadoop.apache.org>
Sent: Wednesday, September 25, 2013 11:29 A= M
Subject: Is there an= y way to partially process HDFS edits?

I= have an edits file on my namenode that is 35GB. This is quite a bit larger= than it should be (the secondary namenode wasn't running for some time, an= d HBASE-9648 caused a huge number of additional edits).
=0A
The first time I tried to start the namenode, it chewed on the edit= s for about 4 hours and then ran out of memory. I have increased the memory= available to the namenode (was 512MB, now 2GB), and started the process ag= ain.
=0A

Is there any way that the edits file can b= e partially processed to avoid having to re-process the same edits over and= over until I can allocate enough memory for it to be done in one shot?
=
=0A
How long should it take (hours? days?) to proc= ess an edits file of that size?

Any help is apprec= iated!

--Tom


--624387052-725184109-1380138830=:85455--