Return-Path: Delivered-To: apmail-lucene-hadoop-user-archive@locus.apache.org Received: (qmail 72462 invoked from network); 10 Jan 2007 16:42:11 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 10 Jan 2007 16:42:11 -0000 Received: (qmail 11118 invoked by uid 500); 10 Jan 2007 16:42:12 -0000 Delivered-To: apmail-lucene-hadoop-user-archive@lucene.apache.org Received: (qmail 11040 invoked by uid 500); 10 Jan 2007 16:42:11 -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 10994 invoked by uid 99); 10 Jan 2007 16:42:11 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Jan 2007 08:42:11 -0800 X-ASF-Spam-Status: No, hits=1.4 required=10.0 tests=DNS_FROM_RFC_ABUSE,DNS_FROM_RFC_WHOIS X-Spam-Check-By: apache.org Received-SPF: neutral (herse.apache.org: local policy) Received: from [207.126.228.149] (HELO rsmtp1.corp.yahoo.com) (207.126.228.149) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Jan 2007 08:42:00 -0800 Received: from coatspeaklx (coatspeak-lx.corp.yahoo.com [10.72.110.26]) (authenticated bits=0) by rsmtp1.corp.yahoo.com (8.13.8/8.13.6/y.rout) with ESMTP id l0AGfbms080589 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Wed, 10 Jan 2007 08:41:37 -0800 (PST) DomainKey-Signature: a=rsa-sha1; s=serpent; d=yahoo-inc.com; c=nofws; q=dns; h=from:to:subject:date:message-id:mime-version:content-type: content-transfer-encoding:x-mailer:x-mimeole:thread-index:in-reply-to; b=ifdIvQcKh1xCSGqYN1YbOh3o2u5StYNo4r00qsJ+Z6n2OlrUew11cUPQeHfu8HP4 From: "Dhruba Borthakur" To: Subject: RE: Name node failover Date: Wed, 10 Jan 2007 08:41:36 -0800 Message-ID: <00b001c734d6$3227bfe0$639115ac@ds.corp.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 Thread-Index: Acc0urpyb0bw8MZGSUKqk8GVmvnbDgAG2BmA In-Reply-To: <3d717a3d0701100455q4531b0c7w434d22be1721b19b@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org Periodic checkpointing is expected to be ready by the end of this month. Thanks, dhruba -----Original Message----- From: Sarvesh Singh [mailto:serveshp@gmail.com] Sent: Wednesday, January 10, 2007 4:56 AM To: hadoop-user@lucene.apache.org Subject: Re: Name node failover Thanks! when is it expected? On 1/10/07, Gautam Kowshik wrote: > > There are plans to implement periodic check pointing of namenode data so > as to be revived quickly after a failure. As of now a namenode revival > is manual and begins from the start. > You can follow this [1] bug for developments on check pointing. > > -Gautam. > [1] - http://issues.apache.org/jira/browse/HADOOP-227 > > Sarvesh Singh wrote: > > Hi, > > > > It looks like name node failover is not yet implemented after seeing > some > > emails over this alias. > > I tested name node failover scenario and it does not work > > When is it expected to get implemented? > > > > Thanks > > Servesh > > > >