Return-Path: X-Original-To: apmail-hadoop-mapreduce-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-mapreduce-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 DBA1B9EAF for ; Tue, 14 May 2013 07:47:51 +0000 (UTC) Received: (qmail 30748 invoked by uid 500); 14 May 2013 07:47:47 -0000 Delivered-To: apmail-hadoop-mapreduce-user-archive@hadoop.apache.org Received: (qmail 30594 invoked by uid 500); 14 May 2013 07:47:46 -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 30574 invoked by uid 99); 14 May 2013 07:47:45 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 May 2013 07:47:45 +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.223.182 as permitted sender) Received: from [209.85.223.182] (HELO mail-ie0-f182.google.com) (209.85.223.182) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 May 2013 07:47:39 +0000 Received: by mail-ie0-f182.google.com with SMTP id a14so393479iee.41 for ; Tue, 14 May 2013 00:47:18 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:content-type:x-gm-message-state; bh=8toF8vFMLKmn+kpZLSnuRC8ohbgGdyKKV1d06bAucMQ=; b=MAe+o6YPO29J97irXHy/3oMxPyuaj+/ek9KdJKsoX4ukdQk90x9W3tIXlpMZapEUQG tDPNqOsV3mH8WjXLQ2D/H5E0zHRMGvrl+aGjm41JijIWverC2QfhA68v+7zAuayzjVDN tsBHLLyw71YgScnghmT0D7jCWEAGy0YdpYpBYo1ug4uC9wyl4cW57yuuvg2LmVbFGLeq k8ClBfVcwZ8vmAETEXvGLx99OguIzM1kzplq33tGiGKaVmdXFn1hstLduwdE6rsGK9jj 18zKusnuc8kQnPK/FWT6ifzZbNwAEbroDybA4GoB0bnumGI+eCu7j9yKcj4sUMtYVy+r 3u8g== X-Received: by 10.50.106.77 with SMTP id gs13mr1226832igb.7.1368517638565; Tue, 14 May 2013 00:47:18 -0700 (PDT) MIME-Version: 1.0 Received: by 10.50.45.41 with HTTP; Tue, 14 May 2013 00:46:58 -0700 (PDT) In-Reply-To: References: From: Harsh J Date: Tue, 14 May 2013 13:16:58 +0530 Message-ID: Subject: Re: Read namenode data from primary memory To: "" Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQnTggXjcB2d95hVo8jO4P3sUfr5/yc44lWiDDkvRhzjsWIkbtgPyIg+Xtc5y3wDVuI5sEdX X-Virus-Checked: Checked by ClamAV on apache.org If you're looking to tail the metadata changes for analysis purposes, there's a more pluggable approach available in 2.x versions. If you're looking to backup the metadata outside of NameNode, I'd suggest ditching such an approach and using 2.x's HA HDFS mode instead. On Tue, May 14, 2013 at 12:07 PM, Aditya exalter wrote: > Hi, > > How to get the namenode data(edits and fsimage) from the main > memory(RAM) > > > > -- Harsh J