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 690F4DE87 for ; Wed, 22 May 2013 03:47:35 +0000 (UTC) Received: (qmail 28685 invoked by uid 500); 22 May 2013 03:47:31 -0000 Delivered-To: apmail-hadoop-user-archive@hadoop.apache.org Received: (qmail 28183 invoked by uid 500); 22 May 2013 03:47:29 -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 28140 invoked by uid 99); 22 May 2013 03:47:28 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 May 2013 03:47:28 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of harsh@cloudera.com designates 209.85.223.176 as permitted sender) Received: from [209.85.223.176] (HELO mail-ie0-f176.google.com) (209.85.223.176) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 May 2013 03:47:22 +0000 Received: by mail-ie0-f176.google.com with SMTP id at1so4096047iec.35 for ; Tue, 21 May 2013 20:47:01 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:x-gm-message-state; bh=3ys8N2QOcXoPQT7HjE1RIjbckTubh6VMxPkX3cyYSag=; b=ZNet57cFJjGlcDGtPGQ0tBYZ6Ti/0e1bedwnRMgtcyfgTZfQn/t/sXK7VhnQqdJDmk OepPiJ1ycAwojPSmG/NiQFSdyk9H3ZcPjDl2wRa+SwiMSibjjBJP3yPb3LfcxjkagnHB eIhpFQ+t5ktlkAd9xGvafqqYXXtjqU4VBDRZJ/I2Nw9Ox+rAOmJCCLw7UBIhn9BM3DmI 4N3nsPCI6KMoCac6GwUfJh7b7nyYNs72JFXsXsQkf4zNl8z4M6SUYb0CtQ9Wksm2pOuD HlI9HdyUrIjyAwQuPnaTbOS1PrrXAnT/h5Rzdt5vDQyNkKl8Lz8K9KmmYHkhPSKcrvuf KtOg== X-Received: by 10.50.128.134 with SMTP id no6mr9953014igb.10.1369194421297; Tue, 21 May 2013 20:47:01 -0700 (PDT) MIME-Version: 1.0 Received: by 10.50.33.39 with HTTP; Tue, 21 May 2013 20:46:40 -0700 (PDT) In-Reply-To: References: <0a9001ce55f5$08eb9b50$1ac2d1f0$@yahoo.com> From: Harsh J Date: Wed, 22 May 2013 09:16:40 +0530 Message-ID: Subject: Re: Recovering the namenode from failure To: "" Content-Type: multipart/alternative; boundary=047d7b10c94b1c3c9a04dd466b35 X-Gm-Message-State: ALoCoQn0tEiT+j2A3wiV2znwHMP4hbI7o7m1cGOFt9cNk1qlj8ojj0lXBw8ZTFqxuy8nXSalrsb1 X-Virus-Checked: Checked by ClamAV on apache.org --047d7b10c94b1c3c9a04dd466b35 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable I think he's mentioned the new NN is the same IP and Hostname as the old one, and uses an actual checkpoint. All he has to do is start the DNs back up again and they should report in fine. On Tue, May 21, 2013 at 10:03 PM, Michael Segel wrote: > I think what he's missing is to change the configurations to point to the > new name node. > > It sounds like the new NN has a different IP address from the old NN so > the DNs don't know who to report to... > > On May 21, 2013, at 11:23 AM, Todd Lipcon wrote: > > Hi David, > > You shouldn't need to do anything to get your DNs to report in -- as best > they can tell, it's the same NN. Do you see any error messages in the DN > logs? > > -Todd > > On Tue, May 21, 2013 at 12:30 AM, David Parks wro= te: > >> I=92m on CDH4, and trying to recover both the namenode and cloudera mana= ger >> VMs from HDFS after losing the namenode.**** >> >> ** ** >> >> All of our backup VMs are on HDFS, so for the moment I just want to hack >> something together, copy the backup VMs off HDFS and get on with properl= y >> reconfiguring via CDH Manger.**** >> >> ** ** >> >> So I=92ve installed a plain =91ol namenode on one of my cluster nodes an= d >> started it with =96importCheckpoint (with the data from the secondary NN= ), >> this seems to have worked, I have a namenode web UI up which expects to >> find 32178 blocks.**** >> >> ** ** >> >> But my plain namenode (on the same hostname and IP as the old namenode) >> says that there are no datanodes in the cluster.**** >> >> ** ** >> >> What do I need in order to configure the datanodes to report their block= s >> into this new namenode (same IP & hostname)?**** >> >> ** ** >> >> Thanks,**** >> >> David**** >> >> ** ** >> > > > > -- > Todd Lipcon > Software Engineer, Cloudera > > > --=20 Harsh J --047d7b10c94b1c3c9a04dd466b35 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable
I think he's mentioned the new NN is the same IP and H= ostname as the old one, and uses an actual checkpoint. All he has to do is = start the DNs back up again and they should report in fine.


On Tue, May 21, 2013 at 10:03 PM, Michae= l Segel <michael_segel@hotmail.com> wrote:
I think what he's missing is to cha= nge the configurations to point to the new name node.=A0

It sounds like the new NN has a different IP address from the old NN so th= e DNs don't know who to report to...=A0

On May 21, 2013, at 11:23 AM, Tod= d Lipcon <todd@cl= oudera.com> wrote:

Hi David,
=
You shouldn't need to do anything to get your DNs to report = in -- as best they can tell, it's the same NN. Do you see any error mes= sages in the DN logs?

-Todd

On Tue, May 21, 2013 at 12:30 AM, David Park= s <davidparks21@yahoo.com> wrote:

I= =92m on CDH4, and trying to recover both the namenode and cloudera manager = VMs from HDFS after losing the namenode.

=A0

All of our backup VMs are on HD= FS, so for the moment I just want to hack something together, copy the back= up VMs off HDFS and get on with properly reconfiguring via CDH Manger.

=A0

So I=92v= e installed a plain =91ol namenode on one of my cluster nodes and started i= t with =96importCheckpoint (with the data from the secondary NN), this seem= s to have worked, I have a namenode web UI up which expects to find 32178 b= locks.

=A0

But my p= lain namenode (on the same hostname and IP as the old namenode) says that t= here are no datanodes in the cluster.

=A0

What do I need in order to conf= igure the datanodes to report their blocks into this new namenode (same IP = & hostname)?

=A0<= /p>

Thanks,

David

=A0




--
Todd Lipcon
Software Engineer, Clouder= a




--
Harsh J --047d7b10c94b1c3c9a04dd466b35--