Return-Path: Delivered-To: apmail-hadoop-core-user-archive@www.apache.org Received: (qmail 85623 invoked from network); 22 Jun 2009 20:25:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 22 Jun 2009 20:25:19 -0000 Received: (qmail 7174 invoked by uid 500); 22 Jun 2009 20:25:28 -0000 Delivered-To: apmail-hadoop-core-user-archive@hadoop.apache.org Received: (qmail 7086 invoked by uid 500); 22 Jun 2009 20:25:28 -0000 Mailing-List: contact core-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-user@hadoop.apache.org Delivered-To: mailing list core-user@hadoop.apache.org Received: (qmail 7076 invoked by uid 99); 22 Jun 2009 20:25:28 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Jun 2009 20:25:28 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of pku.gaoqin@gmail.com designates 209.85.222.201 as permitted sender) Received: from [209.85.222.201] (HELO mail-pz0-f201.google.com) (209.85.222.201) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Jun 2009 20:25:18 +0000 Received: by pzk39 with SMTP id 39so1291541pzk.5 for ; Mon, 22 Jun 2009 13:24:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type; bh=P5efxnR9PBDae/P+6DE69Vswlr1A9iNyrD1ODupz0vM=; b=EcpC2uPh6rv5FaxjinnwwCDwxMpbnKFzZ1Mf7Mtgw+Rycr/CSHmRA99kati/nXrk8A Oi1OPidC21/nkDXCNZTh8lGi3YyehYQi7Oo9ZYhsFw9LvSlC3u+6Dn8Wo2uva8TieoW5 /KeImAtKR/BLrxMl7Y6k5Z6EHlhk2VkTBgHwY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=hXy30ZvWDcp4bDJt6TYGfkw4sOw87dNJ+XWNi/Mpcy++PdCp/ZLmhBBz93R1xUfYCq 5O6IXSntrEfGaCsg0wRaouiyyQxkmXG2uF+2dc8zxuPdPkT3yzcQ2oAX2+9C9+NAGj4h SrNhRdA0kxyjLDFIGh/b5kO5ezg1d4T1t078s= MIME-Version: 1.0 Sender: pku.gaoqin@gmail.com Received: by 10.142.51.1 with SMTP id y1mr2911930wfy.112.1245702297288; Mon, 22 Jun 2009 13:24:57 -0700 (PDT) In-Reply-To: <445c748b0906221319x767f1c92wb63376eb115d848e@mail.gmail.com> References: <826304a60906221215i6c72b0a5ue43722b1504ccc74@mail.gmail.com> <445c748b0906221319x767f1c92wb63376eb115d848e@mail.gmail.com> Date: Mon, 22 Jun 2009 16:24:57 -0400 X-Google-Sender-Auth: 9cf4c64bc45f5db6 Message-ID: <826304a60906221324l10865619v5d96d5322080c847@mail.gmail.com> Subject: Re: Making sure the tmp directory is cleaned? From: Qin Gao To: core-user@hadoop.apache.org Content-Type: multipart/alternative; boundary=000e0cd20ddced00d6046cf5aaf7 X-Virus-Checked: Checked by ClamAV on apache.org --000e0cd20ddced00d6046cf5aaf7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Thanks! But what if the jobs get killed or failed? Does hadoop try to clean it? we are considering bad situations - if job gets killed, will the tmp dirs sit on local disks forever and eats up all the diskspace? I guess this should be considered in distributed cache, but those files are read-only, and our program will generate new temporary files. --Q On Mon, Jun 22, 2009 at 4:19 PM, Pankil Doshi wrote: > Yes, If your job gets completed successfully .possibly it removes after > completion of both map and reduce tasks. > > Pankil > > On Mon, Jun 22, 2009 at 3:15 PM, Qin Gao wrote: > > > Hi All, > > > > Do you know if the tmp directory on every map/reduce task will be deleted > > automatically after the map task finishes or will do I have to delete > them? > > > > I mean the tmp directory that automatically created by on current > > directory. > > > > Thanks a lot > > --Q > > > --000e0cd20ddced00d6046cf5aaf7--