Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 50230 invoked from network); 20 May 2009 14:53:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 20 May 2009 14:53:03 -0000 Received: (qmail 95966 invoked by uid 500); 20 May 2009 14:53:15 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 95913 invoked by uid 500); 20 May 2009 14:53:15 -0000 Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-dev@hadoop.apache.org Delivered-To: mailing list core-dev@hadoop.apache.org Received: (qmail 95903 invoked by uid 99); 20 May 2009 14:53:15 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 May 2009 14:53:15 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of sangmin.dev@gmail.com designates 209.85.219.171 as permitted sender) Received: from [209.85.219.171] (HELO mail-ew0-f171.google.com) (209.85.219.171) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 May 2009 14:53:07 +0000 Received: by ewy19 with SMTP id 19so610506ewy.29 for ; Wed, 20 May 2009 07:52:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=tqvsX2KQG8wMGPFKRWBCtkexZ4UoekTk81jCr8FUYFw=; b=sQwDyy9dLUtBKcwImMFc4/oBEBkb4BVxu5rus4RhVyEIGDV65kr2XX5YlOUiz8i6X7 eM2rRp30MHgmThSWDkiHzLM+T5NBW5mniELQo6O7F9kEjHbDwjlyppKbz7UIcI6YpRfk VJGonzgYTdbFILtEji5BmSzeBEpLhi1d6vOQk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=qDHihe6I54sZr31DNSKFcTMr8f0sc4o35jRIjRO5TbrimsQdX6P6KbYGXj0CqmKpif 0U/KEPZqn4TGXPqAgyu5JlkeQL2BCKR/84Gq+WKvzZyjgnBSOwbOL+6Unim2PNXAfKub GZZnaTWsKeirFIGRDvdCOdFOvQi711v0HEjgc= MIME-Version: 1.0 Received: by 10.216.53.139 with SMTP id g11mr323293wec.25.1242831165913; Wed, 20 May 2009 07:52:45 -0700 (PDT) Date: Wed, 20 May 2009 09:52:45 -0500 Message-ID: <811fc3830905200752i12cb53ejf9c77327db9f0999@mail.gmail.com> Subject: HDFS recovery code question From: Sangmin Lee To: core-dev@hadoop.apache.org Content-Type: multipart/alternative; boundary=0016e6dd940e28fd2e046a592e5a X-Virus-Checked: Checked by ClamAV on apache.org --0016e6dd940e28fd2e046a592e5a Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi all, I have some question regarding the hdfs recovery mechanism. I see that INodeFileUnderConstruction has a "targets" field that stores list of datanodes which store its last block. However, I don't see them being used at all except that "internalReleaseLease" function uses the length of the datanode list. Is there any other use of the "target" fields rather than checking its length? Could anyone shed some light on this? Thanks, Sangmin --0016e6dd940e28fd2e046a592e5a--