Return-Path: Delivered-To: apmail-lucene-hadoop-user-archive@locus.apache.org Received: (qmail 66715 invoked from network); 25 Aug 2007 02:19:52 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 25 Aug 2007 02:19:52 -0000 Received: (qmail 64653 invoked by uid 500); 25 Aug 2007 02:19:47 -0000 Delivered-To: apmail-lucene-hadoop-user-archive@lucene.apache.org Received: (qmail 64631 invoked by uid 500); 25 Aug 2007 02:19:47 -0000 Mailing-List: contact hadoop-user-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hadoop-user@lucene.apache.org Delivered-To: mailing list hadoop-user@lucene.apache.org Received: (qmail 64621 invoked by uid 99); 25 Aug 2007 02:19:47 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Aug 2007 19:19:47 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jssarma@facebook.com designates 204.15.23.140 as permitted sender) Received: from [204.15.23.140] (HELO SF2PMXF01.TheFacebook.com) (204.15.23.140) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 25 Aug 2007 02:19:40 +0000 Received: from SF2PMXB01.TheFacebook.com ([192.168.16.15]) by SF2PMXF01.TheFacebook.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 24 Aug 2007 19:21:01 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Subject: RE: secondary namenode errors Date: Fri, 24 Aug 2007 19:20:59 -0700 Message-ID: In-Reply-To: <46CEF93B.3080801@yahoo-inc.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: secondary namenode errors Thread-Index: AcfmY9EVGCpNMAsBSoydnf4B7O9NxQAWk6sQ From: "Joydeep Sen Sarma" To: X-OriginalArrivalTime: 25 Aug 2007 02:21:01.0463 (UTC) FILETIME=[9499CA70:01C7E6BE] X-Virus-Checked: Checked by ClamAV on apache.org I wish I had read the bug more carefully - thought that the issue was fixed in 0.13.1. Of course not, the issue persists. Meanwhile - half the files are corrupted after the upgrade (followed the upgrade wiki, tried to restore to backed up metadata and old version - to no avail). Sigh - have a nice weekend everyone, Joydeep -----Original Message----- From: Koji Noguchi [mailto:knoguchi@yahoo-inc.com]=20 Sent: Friday, August 24, 2007 8:29 AM To: hadoop-user@lucene.apache.org Subject: Re: secondary namenode errors Joydeep, I think you're hitting this bug. http://issues.apache.org/jira/browse/HADOOP-1076 In any case, as Raghu suggested, please use 0.13.1 and not 0.13. Koji Raghu Angadi wrote: > Joydeep Sen Sarma wrote: >> Thanks for replying. >> >> Can you please clarify - is it the case that the secondary namenode >> stuff only works in 0.13.1? and what's the connection with replication >> factor? >> >> We lost the file system completely once, trying to make sure we can >> avoid it the next time. > > I am not sure if the problem you reported still exists in 0.13.1. You=20 > might still have the problem and you can ask again. But you should=20 > move to 0.13.1 since it has some critical fixes. See release notes for > 0.13.1 or HADOOP-1603. You should always upgrade to the latest minor=20 > release version when moving to next major version. > > Raghu. > >> Joydeep >> >> -----Original Message----- >> From: Raghu Angadi [mailto:rangadi@yahoo-inc.com] Sent: Thursday,=20 >> August 23, 2007 9:44 PM >> To: hadoop-user@lucene.apache.org >> Subject: Re: secondary namenode errors >> >> >> On a related note, please don't use 0.13.0, use the latest released=20 >> version for 0.13 (I think it is 0.13.1). If the secondary namenode=20 >> actually works, then it will resulting all the replications set to 1. >> >> Raghu. >> >> Joydeep Sen Sarma wrote: >>> Hi folks,