Return-Path: 
 <user-return-1692-apmail-hadoop-hdfs-user-archive=hadoop.apache.org@hadoop.apache.org>
X-Original-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org
Delivered-To: apmail-hadoop-hdfs-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 6B1579745
	for <apmail-hadoop-hdfs-user-archive@minotaur.apache.org>;
 Fri, 28 Sep 2012 09:21:47 +0000 (UTC)
Received: (qmail 85402 invoked by uid 500); 28 Sep 2012 09:21:42 -0000
Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org
Received: (qmail 84907 invoked by uid 500); 28 Sep 2012 09:21:36 -0000
Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@hadoop.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@hadoop.apache.org>
List-Post: <mailto:user@hadoop.apache.org>
List-Id: <user.hadoop.apache.org>
Reply-To: user@hadoop.apache.org
Delivered-To: mailing list user@hadoop.apache.org
Received: (qmail 84886 invoked by uid 99); 28 Sep 2012 09:21:36 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Sep 2012 09:21:36 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=FSL_RCVD_USER,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of dechouxb@gmail.com designates
 209.85.216.41 as permitted sender)
Received: from [209.85.216.41] (HELO mail-qa0-f41.google.com) (209.85.216.41)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Sep 2012 09:21:29 +0000
Received: by qatp27 with SMTP id p27so5894548qat.14
        for <user@hadoop.apache.org>; Fri, 28 Sep 2012 02:21:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:date:message-id:subject:from:to:content-type;
        bh=gcYrLIudO1txpHikXuSJTzD/xuQMPQ0yTz+RyhtDLTY=;
        b=WknZ6um5Ihs0PNcL9KnpYjPftqEgkSgVk3uDnR3vwKy8tP4bnYXLsLbadlEp1MJfee
         q4fI12qWN9kbRD8Gg43yBfRgJbj+5+zziJkTMnQpCCc/rBKjKwOEDEEy8LS4nS3YmXTr
         2Z1cTvwQpI2dYNEeXq/tSCUXdywC5yOsqySIF/LYo0epkMEuGf2n395xrfUS+VHGISO+
         OGIqYzNlDKyoZfi6mE6mB9rLfUASmjIwxr9dcwycqy+cezQTEcHqdcFFDiiVrb9nW3mH
         4HPYlRPsMCanGWFxld3dCFEz3Qng0AQWHJRQu5HCwaMQBgy6U8iLaFzQYRcpDC+mYpoF
         IRCg==
MIME-Version: 1.0
Received: by 10.224.168.83 with SMTP id t19mr15824974qay.8.1348824068950; Fri,
 28 Sep 2012 02:21:08 -0700 (PDT)
Received: by 10.49.71.231 with HTTP; Fri, 28 Sep 2012 02:21:08 -0700 (PDT)
Date: Fri, 28 Sep 2012 11:21:08 +0200
Message-ID: 
 <CAO6W-2d5EANtPERQKWgyV2aBv+F2mQRnRzUoQGyOi_nt5w4Ahg@mail.gmail.com>
Subject: dfs.name.dir replication and disk not available
From: Bertrand Dechoux <dechouxb@gmail.com>
To: user@hadoop.apache.org
Content-Type: multipart/alternative; boundary=20cf3074b5ce7e88ae04cabf9399
X-Virus-Checked: Checked by ClamAV on apache.org

--20cf3074b5ce7e88ae04cabf9399
Content-Type: text/plain; charset=ISO-8859-1

Hi,

I was wondering about the safety of multiples dfs.name.dir directories.
On one hand, we want all copies to be synchronised but on the other hand if
a hard drive fail we would like the namenode still to be operational.
How does that work? I know there is the source but I was hoping for a
higher level description.

Regards

Bertrand

PS : I am interested about the behaviour of the last stable version ie
1.0.3. Not in the old issues that were solved.

--20cf3074b5ce7e88ae04cabf9399
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi,<br><br>I was wondering about the safety of multiples dfs.name.dir direc=
tories.<br>On one hand, we want all copies to be synchronised but on the ot=
her hand if a hard drive fail we would like the namenode still to be operat=
ional.<br>
How does that work? I know there is the source but I was hoping for a highe=
r level description.<br><br>Regards<br><br>Bertrand<br clear=3D"all"><br>PS=
 : I am interested about the behaviour of the last stable version ie 1.0.3.=
 Not in the old issues that were solved.<br>


--20cf3074b5ce7e88ae04cabf9399--