Return-Path: Delivered-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org Received: (qmail 38851 invoked from network); 9 Feb 2010 01:11:32 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 9 Feb 2010 01:11:32 -0000 Received: (qmail 59448 invoked by uid 500); 9 Feb 2010 01:11:31 -0000 Delivered-To: apmail-hadoop-hdfs-dev-archive@hadoop.apache.org Received: (qmail 59357 invoked by uid 500); 9 Feb 2010 01:11:31 -0000 Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-dev@hadoop.apache.org Delivered-To: mailing list hdfs-dev@hadoop.apache.org Received: (qmail 59347 invoked by uid 99); 9 Feb 2010 01:11:31 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Feb 2010 01:11:31 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [209.85.222.175] (HELO mail-pz0-f175.google.com) (209.85.222.175) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Feb 2010 01:11:23 +0000 Received: by pzk5 with SMTP id 5so6868760pzk.29 for ; Mon, 08 Feb 2010 17:11:02 -0800 (PST) MIME-Version: 1.0 Received: by 10.142.249.15 with SMTP id w15mr4811250wfh.288.1265677862269; Mon, 08 Feb 2010 17:11:02 -0800 (PST) In-Reply-To: <45f85f71002081645n3fe41e7btcbe0c214db6b6fd@mail.gmail.com> References: <45f85f71002081645n3fe41e7btcbe0c214db6b6fd@mail.gmail.com> From: Todd Lipcon Date: Mon, 8 Feb 2010 17:10:42 -0800 Message-ID: <45f85f71002081710v5dc21a4fifdc986c9974dcf4f@mail.gmail.com> Subject: Re: Name Node Corruption When Shutdown Too Soon To: hdfs-dev@hadoop.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org Hi Jonathan, Another question: how have you configured dfs.name.dir? Do you have several directories configured? Thanks -Todd On Mon, Feb 8, 2010 at 4:45 PM, Todd Lipcon wrote: > Hey Jonathan, > > As Konstantin mentioned, I've been looking into a couple issues that > could be related. At first glance it doesn't sound like you've run > into quite the same thing. > > What version did you see this on? The steps to reproduce are something li= ke: > > 1) Start a NN > 2) Perform a bunch of edits so there is a large edit log > 3) kill -9 the NN > 4) start the NN again > 5) while it is in the middle of replaying edits, kill -9 it again > 6) start the NN, and lose all the previous edits? > > Or did I misunderstand what happened? If that sounds right, I'll give > it a go and see if I can reproduce. > > Thanks > -Todd > > On Sun, Feb 7, 2010 at 8:45 AM, Allen, Jonathan = wrote: >> I've come across a name node bug and just wanted to check if it's a know= n issue before I formally raise it (I've had a quick look through the datab= ase but couldn't see anything obvious). >> >> If the name node is shut down before it has completed reading through th= e edit log then the edit log gets removed without the image file being upda= ted. =A0This results in name node reverting to its previously saved state (= out of sync with the data nodes) and the most recent edits getting lost. >> >> Does anybody recognise this as a known issue or should I raise it? >> >> Thanks, >> Jonathan Allen >> UKGP, NS&R, Defence and Security >> HP Enterprise Services >> Telephone +44 1682 292101 >> Email jonathan.allen.uk@hp.com >> Street address, Unit 29, Alexandra Way, Ashchurch Business Park, Tewkesb= ury, Gloucestershire. GL20 8NB >> >> Hewlett-Packard Limited registered Office: Cain Road, Bracknell, Berks R= G12 1HN >> Registered No: 690597 England >> The contents of this message and any attachments to it are confidential = and may be legally privileged. If you have received this message in error, = you should delete it from your system immediately and advise the sender. >> To any recipient of this message within HP, unless otherwise stated you = should consider this message and attachments as "HP CONFIDENTIAL". >> >> >> >> >