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 229A3F954 for ; Mon, 2 Sep 2013 08:17:46 +0000 (UTC) Received: (qmail 16164 invoked by uid 500); 2 Sep 2013 08:17:38 -0000 Delivered-To: apmail-hadoop-mapreduce-user-archive@hadoop.apache.org Received: (qmail 15988 invoked by uid 500); 2 Sep 2013 08:17: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 15639 invoked by uid 99); 2 Sep 2013 08:17:38 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Sep 2013 08:17:38 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of nitinpawar432@gmail.com designates 209.85.214.176 as permitted sender) Received: from [209.85.214.176] (HELO mail-ob0-f176.google.com) (209.85.214.176) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Sep 2013 08:17:32 +0000 Received: by mail-ob0-f176.google.com with SMTP id uz19so4201979obc.21 for ; Mon, 02 Sep 2013 01:17:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=OYe9PjLigMSaBcJVYyV+2cOlbeX011FPfTkdjvDLVjw=; b=OVZ5wyhZwNOZ/2dWJdLjSPWcmuXsk80aAJL4NfK9EymBy+6D23rP3NCfCh9MLamor7 T+wZRZJHk5KT3BEfhhRndBKLEEt2yGoH2gdIG1ZH6IH5OxRMvB+uvMNFKIATK2WKjt9/ Opq10a0sz65bt0wWz8oNm56eBSxCUmxamtvHVc2H4iyb3EQYkGz7H1RWT8QGzehpWm4D 6qdcLb1Ijv+Q+MwZGoNvwP+8aAHvFAfdtYgpS3dN/H3Fw5cDjosxVrDp40wS8dXYdg6F UOwaP/hhqg1whzP109Tmdvjio1eouRjzm85n4bPTiMoG5eXitWGC1NAYO6GNBG45vwUP X3fA== MIME-Version: 1.0 X-Received: by 10.182.230.135 with SMTP id sy7mr15944873obc.24.1378109832235; Mon, 02 Sep 2013 01:17:12 -0700 (PDT) Received: by 10.182.158.163 with HTTP; Mon, 2 Sep 2013 01:17:12 -0700 (PDT) In-Reply-To: References: Date: Mon, 2 Sep 2013 13:47:12 +0530 Message-ID: Subject: Re: Can the /tmp directory be cleaned? From: Nitin Pawar To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=001a11c3367603117204e5623383 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c3367603117204e5623383 Content-Type: text/plain; charset=ISO-8859-1 /tmp on hadoop or /tmp on local machine? if its local machine then look at command "tmpwatch" Normally anything inside /tmp should be cleanable after the processes are over On Mon, Sep 2, 2013 at 1:31 PM, Pavan Sudheendra wrote: > Hi all, > We have many Hadoop, Hbase, Pig jobs running and strangely the /tmp > directory is also building in size. Out default filesystem is limited in > memory so can we go ahead and delete the contents? > > Thanks. > > -- > Regards- > Pavan > -- Nitin Pawar --001a11c3367603117204e5623383 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
/tmp on hadoop or /tmp on local machine?=A0
if its loc= al machine then look at command "tmpwatch"=A0

Normally anything inside /tmp should be cleanable after the processes= are over =A0


On Mon,= Sep 2, 2013 at 1:31 PM, Pavan Sudheendra <pavan0591@gmail.com> wrote:
Hi all,
= We have many Hadoop, Hbase, Pig jobs running and strangely the /tmp directo= ry is also building in size. Out default filesystem is limited in memory so= can we go ahead and delete the contents?

Thanks.

--
Regards-
Pavan



--
Nitin Pawar<= br>
--001a11c3367603117204e5623383--