Mailing-List: contact core-user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-user@hadoop.apache.org
Received-SPF: pass (athena.apache.org: domain of slunati@gmail.com designates
 64.233.170.190 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:mime-version:content-type;
        b=YP+YKVIIFW4EUTQBN0YAaxZ5p5LbFr9GmQ/pBYdDuvqVxO+r+GLOBiUfX6jBYFdAtv
         8h/4BnMN9sEylo60rMzoLIt1G+Lw89Yh0wXoBTTwlef0Vbo2tfjO93YdlHGpjJ5lf485
         EtbKDNnonXhukj4ZTRl0gf7ziq1urkk1WbczM=
Message-ID: <2b94eb950811131718u7501f9b6w66db433abe6cbba5@mail.gmail.com>
Date: Thu, 13 Nov 2008 17:18:40 -0800
From: S.L. <slunati@gmail.com>
To: core-user@hadoop.apache.org
Subject: HDFS NameNode and HA: best strategy?
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_39916_30627761.1226625520827"

------=_Part_39916_30627761.1226625520827
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi list
I am kind of new to Hadoop but have some good background. I am seriously
considering adopting Hadoop and especially HDFS first to be able to store
various files (in the low hundreds thousands at first) on a few nodes in a
manner where I don't need a RAID system or a SAN. HDFS seems a perfect fit
for the job...

BUT

from what I learn in the past couple days it seems that the single point of
failure in HDFS is the NameNode. So I was wondering if anyone in the list
that did deploy HDFS in a production environment on what is their strategy
for High Availability of the system... Having the NameNode unavailable is
basically bringing the whole HDFS system offline. So what are the scripts or
other techniques recommended to add H.A to HDFS !

Thank !

-- S.

------=_Part_39916_30627761.1226625520827--