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 669C210134 for ; Fri, 31 Jan 2014 10:40:56 +0000 (UTC) Received: (qmail 73947 invoked by uid 500); 31 Jan 2014 10:40:49 -0000 Delivered-To: apmail-hadoop-mapreduce-user-archive@hadoop.apache.org Received: (qmail 73195 invoked by uid 500); 31 Jan 2014 10:40:38 -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 73187 invoked by uid 99); 31 Jan 2014 10:40:37 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 31 Jan 2014 10:40:37 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of rao.jyoti26yadav@gmail.com designates 74.125.82.41 as permitted sender) Received: from [74.125.82.41] (HELO mail-wg0-f41.google.com) (74.125.82.41) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 31 Jan 2014 10:40:31 +0000 Received: by mail-wg0-f41.google.com with SMTP id n12so586465wgh.0 for ; Fri, 31 Jan 2014 02:40:10 -0800 (PST) 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=klny/IIbaQbzQsPQpX8gcmgU4n4wJG5LseKjx8U7yr0=; b=McLMc8yaydzZqxgXCkLjMZT3/MM+U/WnkyFEkCQsHj1MNpGvs1Xak7DNv+x0KSd386 K3sAudchLukinf7DEfjfFKHIvWuLmtdEY7+qj07oZS02Cy1/DEbhcn1beZOAE4QvdbYc AdUOdIfEgXk2nNAVukAxOoSdQZs6vLRwNGgKpbI73Fm+igE+OoaSqCRnaRfvZ5rr+ocV MbBSfs3UTdsn0GPrpgFN5TecM4elDjAIp5nrGo+B//Wqy/NYdhhuir2DcKanB8LTdREt PPYQJxDRMy3BrKIqCPRFyLHGhIMoYckBewMh5x+oPChVJcesqkZjQif+KjOoYFd3hiX0 ItzQ== MIME-Version: 1.0 X-Received: by 10.194.21.193 with SMTP id x1mr11893743wje.33.1391164810680; Fri, 31 Jan 2014 02:40:10 -0800 (PST) Received: by 10.194.3.35 with HTTP; Fri, 31 Jan 2014 02:40:10 -0800 (PST) Date: Fri, 31 Jan 2014 16:10:10 +0530 Message-ID: Subject: About formatting of namenode.. From: Jyoti Yadav To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=047d7b5d56105d5c4504f141cc16 X-Virus-Checked: Checked by ClamAV on apache.org --047d7b5d56105d5c4504f141cc16 Content-Type: text/plain; charset=ISO-8859-1 Hi folks.. I have some doubt while thinking of formatting of namenode.. Actually i am doing my project in Apache Giraph which makes use of hadoop environment to run the job.. While running various job,i noticed that /app/hadoop/tmp/dfs/name/data directory is almost full.. Should i format my namenode?? Will it create any problem?? I know if i format ,i will lose all my data residing in hdfs. Before formatting it,i will take backup of all the input files used to run giraph job.. Seeking your suggestions.. Thanks --047d7b5d56105d5c4504f141cc16 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

Hi folks..

I have some doubt w= hile thinking of formatting of namenode..

Actually i am doing my p= roject in Apache Giraph which makes use of hadoop environment to run the jo= b..

While running various job,i noticed that=A0

/app/hadoop/tmp/dfs/name/data=A0

=A0=A0 directory is almost full= ..

Should i format my namenode??=A0 Will it create any problem??
= I know if i format ,i will lose all my data residing in hdfs.
Before for= matting it,i will take backup of all the input files used to run giraph job= ..

Seeking your suggestions..
Thanks

--047d7b5d56105d5c4504f141cc16--