Return-Path: 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 4A0C210096 for ; Tue, 4 Feb 2014 07:44:06 +0000 (UTC) Received: (qmail 92782 invoked by uid 500); 4 Feb 2014 07:43:58 -0000 Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org Received: (qmail 92508 invoked by uid 500); 4 Feb 2014 07:43:49 -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 92496 invoked by uid 99); 4 Feb 2014 07:43:46 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Feb 2014 07:43:46 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of harsh@cloudera.com designates 209.85.213.182 as permitted sender) Received: from [209.85.213.182] (HELO mail-ig0-f182.google.com) (209.85.213.182) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Feb 2014 07:43:41 +0000 Received: by mail-ig0-f182.google.com with SMTP id uy17so6763439igb.3 for ; Mon, 03 Feb 2014 23:43:20 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=zmjWPrBnkY7VTfVaTWnlgjWkm5DFEI/FR53gwGhkJkU=; b=OWHQjuSIlS+uLVy0SVW9RCPvBoiMoPqkivXGdoLA59b/PAvrRzlW1Ny35Bgu+2m4hb NWld2ob3npeXnT63nmtf0ByrIIqoa80M6fei9EnGs3AU65DkoEv12wjxJ3XMzHBDTwOc yuYip9XVZ45wPKUU5kGuMQ3eQIMNfedfruzuob8/hm5A8A2qoT5JhEWxWvcGYAroL2ms qUhRDzXMonS7F+KFwG7bwGxWstauW4HqE+AcDiQ4tXIPHKTH+RDh2siow2m6kH1rNBMk lDmEco0t0hKVHIBU+zz2R4rf53eNk23Iv9TAGk3fkpJlAPwfzDGqwjC9MGaLu6vClgVm Qd2g== X-Gm-Message-State: ALoCoQmLqfsm4x/VFZf4zmLUJy/ogAfIjGH/4a4UIxeuYO+D//021k7RwFKv0gJK03W/wQKDiziH X-Received: by 10.43.98.202 with SMTP id cp10mr30365925icc.28.1391499800206; Mon, 03 Feb 2014 23:43:20 -0800 (PST) MIME-Version: 1.0 Received: by 10.50.61.97 with HTTP; Mon, 3 Feb 2014 23:42:57 -0800 (PST) In-Reply-To: References: From: Harsh J Date: Tue, 4 Feb 2014 13:12:57 +0530 Message-ID: Subject: Re: Backup NameNode metadata in HA configuration To: "" Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org Nothing wrong in copying it - except it would come with a bunch of redundant information (extra retained edit logs already merged into one of the recent fsimages). On Tue, Feb 4, 2014 at 12:07 PM, Ivan Tretyakov wrote: > Thank you Harsh! > But I would like to know if just copying NN data directory (dfs.name.dir, > dfs.namenode.name.dir) is appropriate or not? > > > On Tue, Feb 4, 2014 at 6:00 AM, Harsh J wrote: >> >> Hi, >> >> You'll ideally just need the latest >> fsimage file, which includes the whole check pointed namespace, so >> "hdfs dfsadmin -fetch" is appropriate. >> >> On Tue, Feb 4, 2014 at 3:02 AM, Ivan Tretyakov >> wrote: >> > Does anybody can comment 'copying NN metadata directory' vs 'hdfs >> > dfsadmin >> > -fetch', using NN HA configuration? >> > >> > >> > On Fri, Jan 31, 2014 at 8:26 PM, Ivan Tretyakov >> > wrote: >> >> >> >> Hi! >> >> >> >> We are using following version of Hadoop software: 2.0.0-cdh4.1.1. >> >> >> >> HDFS HA configuration is applied. >> >> >> >> I would like to ask if there are any difference or possible side >> >> effects >> >> of backing up namenode data directory. >> >> >> >> It is ok to just copy NN data directory from active NN to another host, >> >> what about standby NN? >> >> Or it may NN metadate can be in inconsistent state? >> >> Is there any advantages of using "hdfs dfsadmin -fetch " command? >> >> >> >> -- >> >> Best Regards >> >> Ivan Tretyakov >> >> >> >> Deployment Engineer >> >> Grid Dynamics >> >> +7 812 640 38 76 >> >> Skype: ivan.v.tretyakov >> >> www.griddynamics.com >> >> itretyakov@griddynamics.com >> > >> > >> > >> > >> > -- >> > Best Regards >> > Ivan Tretyakov >> > >> > Deployment Engineer >> > Grid Dynamics >> > +7 812 640 38 76 >> > Skype: ivan.v.tretyakov >> > www.griddynamics.com >> > itretyakov@griddynamics.com >> >> >> >> -- >> Harsh J > > > > > -- > Best Regards > Ivan Tretyakov > > Deployment Engineer > Grid Dynamics > +7 812 640 38 76 > Skype: ivan.v.tretyakov > www.griddynamics.com > itretyakov@griddynamics.com -- Harsh J