Return-Path: X-Original-To: apmail-hadoop-common-user-archive@www.apache.org Delivered-To: apmail-hadoop-common-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3862BDA14 for ; Thu, 22 Nov 2012 17:34:09 +0000 (UTC) Received: (qmail 52364 invoked by uid 500); 22 Nov 2012 17:34:04 -0000 Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org Received: (qmail 52142 invoked by uid 500); 22 Nov 2012 17:34:04 -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 52134 invoked by uid 99); 22 Nov 2012 17:34:04 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Nov 2012 17:34:04 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.223.176] (HELO mail-ie0-f176.google.com) (209.85.223.176) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Nov 2012 17:33:59 +0000 Received: by mail-ie0-f176.google.com with SMTP id 13so6851783iea.35 for ; Thu, 22 Nov 2012 09:33:38 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=1qBViQx0m6msDbt3rVrtI+aVggQSMlBBJGQwX6959zA=; b=jguvglRKrEQa+/Pklk8F1J3MFfiNqXz7OXL1BdcwFMf3KxaO07tdcpmUygNeZtQ1aT mVV5xf2zWEBNmEMYuktxJmQMSTrJeLsckX71dkey/4HalF4tcc0yXjoMw+F4lbXWCpLu TY8je3EFFB9vAY748cHvElhB29T8A0W4HgHTJADnjWjHBNMZzDmlr1uFoutgyCA/Zt+6 3K3R9wSWqrcbZxu+VsToWs/JxsdQWyNZTyrP/rHcqwmqH4ZAdp7dFti9H25SPbMlaflP wbo4OZbjAwSlOjno10ewCCNMr2Odmzs7i9jrBePq9isUIiiVqBBcnsZ3mHEk7x/wihKO SqnA== MIME-Version: 1.0 Received: by 10.50.168.102 with SMTP id zv6mr4041219igb.9.1353605617927; Thu, 22 Nov 2012 09:33:37 -0800 (PST) Received: by 10.64.15.42 with HTTP; Thu, 22 Nov 2012 09:33:37 -0800 (PST) In-Reply-To: References: Date: Thu, 22 Nov 2012 12:33:37 -0500 Message-ID: Subject: Re: CheckPoint Node From: Jean-Marc Spaggiari To: user@hadoop.apache.org Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQmP4umEfwEozy1UvA8/zeBT2Y4WV+N2MWjUmQtsdx4JN4aJKdu/nJIPg9hizHL9nz+/j1I8 X-Virus-Checked: Checked by ClamAV on apache.org Hi Harsh, Thanks for pointing me to this link. I will take a close look at it. So with 1.x and 0.23.x, what's the impact on the data if the namenode server hard-drive die? Is there any critical data stored locally? Or I simply need to build a new namenode, start it and restart all my namenodes to find my data back? I can deal with my application not beeing available, but loosing data can be a bigger issue. Thanks, JM 2012/11/22, Harsh J : > Hey Jean, > > The 1.x, 0.23.x release lines both don't have NameNode HA features. > The current 2.x releases carry HA-NN abilities, and this is documented > at > http://hadoop.apache.org/docs/current/hadoop-yarn/hadoop-yarn-site/HDFSHighAvailability.html. > > On Thu, Nov 22, 2012 at 10:18 PM, Jean-Marc Spaggiari > wrote: >> Replying to myself ;) >> >> By digging a bit more I figured that 1.0 version is older than 0.23.4 >> version and that backupnodes are on 0.23.4. Secondarynamenodes on 1.0 >> are now deprecated. >> >> I'm still a bit mixed up on the way to achieve HA for the namenode >> (1.0 or 0.23.4) but I will continue to dig over internet. >> >> JM >> >> 2012/11/22, Jean-Marc Spaggiari : >>> Hi, >>> >>> I'm reading a bit about hadoop and I'm trying to increase the HA of my >>> current cluster. >>> >>> Today I have 8 datanodes and one namenode. >>> >>> By reading here: http://www.aosabook.org/en/hdfs.html I can see that a >>> Checkpoint node might be a good idea. >>> >>> So I'm trying to start a checkpoint node. I looked at the hadoop >>> online doc. There is a link toe describe the command usage "For >>> command usage, see namenode." but this link is not working. Also, if I >>> try hadoop-deamon.sh start namenode -checkpoint as discribed in the >>> documentation, it's not starting. >>> >>> So I'n wondering, is there anywhere where I can find up to date >>> documentation about the checkpoint node? I will most probably try the >>> BackupNode. >>> >>> I'm using hadoop 1.0.3. The options I have to start on this version >>> are namenode, secondarynamenode, datanode, dfsadmin, mradmin, fsck and >>> fs. Should I start some secondarynamenodes instead of backupnode and >>> checkpointnode? >>> >>> Thanks, >>> >>> JM >>> > > > > -- > Harsh J >