Mailing-List: contact common-user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-user@hadoop.apache.org
Received-SPF: pass (nike.apache.org: domain of Ivan.Novick@emc.com designates
 128.222.32.20 as permitted sender)
From: <Ivan.Novick@emc.com>
To: <common-user@hadoop.apache.org>
Date: Fri, 23 Sep 2011 13:25:55 -0400
Subject: Re: formatting hdfs without user interaction
Thread-Topic: formatting hdfs without user interaction
Thread-Index: Acx6FafrQdsiysPhRSSYfpIjHY4USQ==
Message-ID: <CAA20ED0.A5E1%ivan.novick@emc.com>
In-Reply-To: 
 <CAOcnVr0sMVwJct739quED-Rc51A0KNHgYHYF4PT8-B=n05cqxg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.0.0.100825
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

On 9/23/11 9:46 AM, "Harsh J" <harsh@cloudera.com> wrote:

>Ivan,
>
>On Fri, Sep 23, 2011 at 9:22 PM,  <Ivan.Novick@emc.com> wrote:
>[snip]
>> Which parameter are you referring to? I am planning on using 2
>>directories
>> in dfs.name.dir, one is local and the other is an NFS mount of a 2nd
>> machine running the secondary namenode.
>
>I'm slightly confused here. Do you mean to say a 'SecondaryNameNode',
>which is a form of checkpointing daemon available as part of Hadoop,
>or do you mean to say, loosely, 'secondary namenode', which would
>imply a machine that can step in as a NameNode once you start it (in
>case the primary fails)?
>
>For the former, the properties are the ones that begin with
>"fs.checkpoint.*" in 0.20.x versions, which you can checkout.

I mean both... A 2nd node which can step in as a name node and also that
node will run the checkpointing daemon.  I have 2 directories in
dfs.name.dir one is local and one is remote on the 2nd machine so we have
a copy of the data if we lose the first machine.

Cheers,
Ivan