Received: by 10.204.80.25 with SMTP id r25mr109777bkk.11.1302796336333;
        Thu, 14 Apr 2011 08:52:16 -0700 (PDT)
X-BeenThere: hugid@googlegroups.com
Received: by 10.204.138.67 with SMTP id z3ls3590465bkt.0.p; Thu, 14 Apr 2011
 08:52:15 -0700 (PDT)
Received: by 10.204.14.195 with SMTP id h3mr110021bka.22.1302796335283;
        Thu, 14 Apr 2011 08:52:15 -0700 (PDT)
Received: by 10.204.14.195 with SMTP id h3mr110020bka.22.1302796335209;
        Thu, 14 Apr 2011 08:52:15 -0700 (PDT)
Return-Path: <ifnub...@gmail.com>
Received: from mail-bw0-f53.google.com (mail-bw0-f53.google.com [209.85.214.53])
        by gmr-mx.google.com with ESMTPS id e15si294611bke.1.2011.04.14.08.52.15
        (version=TLSv1/SSLv3 cipher=OTHER);
        Thu, 14 Apr 2011 08:52:15 -0700 (PDT)
Received-SPF: pass (google.com: domain of ifnub...@gmail.com designates 209.85.214.53 as permitted sender) client-ip=209.85.214.53;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of ifnub...@gmail.com designates 209.85.214.53 as permitted sender) smtp.mail=ifnub...@gmail.com; dkim=pass (test mode) header...@gmail.com
Received: by bwg12 with SMTP id 12so2868490bwg.26
        for <hugid@googlegroups.com>; Thu, 14 Apr 2011 08:52:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:mime-version:in-reply-to:references:date
         :message-id:subject:from:to:cc:content-type;
        bh=l3TmQSHPesLt46ZMBs/E+5Gtm0So4I+ph7mpJiWdm44=;
        b=TYoGcPpQfFVfpiSnYLFAzioU70PN+jQyjUHmBCFkFHGNSnsPc7MpHcVbAaJRO0wsnQ
         IjUl8Uxk08WtCxt4vIHX/G1/3FmvbSsIcFXfi8yZV33oY9KbWhdViLJDN/7sVSbKSeWN
         /NLKfOnwPBZhZfUUL4QsoRcwV3iP66KrvG00U=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type;
        b=BSeTqDSvlTiU/9XWk9s+jWxybi1tpDQ0uQLFFSAuX8ATlflbME0qnFYlAk3WtsBrXV
         t1DhucZSrKBb02LGQ6MB/3IkHzrPmXwaVvj/ZcAC6nsvV86cKAE40LEJyBp9Hmt5hjSw
         Gzwa/T8vvPDpMyUFeIy5mplxKVgQK10FH0AjA=
MIME-Version: 1.0
Received: by 10.204.229.193 with SMTP id jj1mr793457bkb.21.1302796334982; Thu,
 14 Apr 2011 08:52:14 -0700 (PDT)
Received: by 10.204.81.167 with HTTP; Thu, 14 Apr 2011 08:52:14 -0700 (PDT)
In-Reply-To: <BANLkTimO6f1jtK3uC=JW8q6FzNDuX=O...@mail.gmail.com>
References: <BANLkTimO6f1jtK3uC=JW8q6FzNDuX=O...@mail.gmail.com>
Date: Thu, 14 Apr 2011 23:52:14 +0800
Message-ID: <BANLkTinaPP_kTixR5AyzFXtESaPi_4f...@mail.gmail.com>
Subject: Re: [hugid] Namenode Failover
From: Ifnu bima <ifnub...@gmail.com>
To: hugid@googlegroups.com
Cc: Feris Thia <fe...@phi-integration.com>
Content-Type: text/plain; charset=ISO-8859-1

> Hi All,
> Mau tanya, kalau primary namenode di Hadoop mengalami masalah... apakah ada yang pernah menggunakan fasilitas / script yang bisa automate failover ke secondary namenode ? Please advice.

kayaknya pernah baca kalau facebook bisa bikin bagian "single point
failure" ini menjadi reliable, alias primary namenode mati ada yang
gantiin. coba ubek2 facebook engineering blog ini deh :

http://www.facebook.com/Engineering

--
http://ifnubima.org/indo-java-podcast/
@ifnubima

regards