Return-Path: 
 <mapreduce-dev-return-8365-apmail-hadoop-mapreduce-dev-archive=hadoop.apache.org@hadoop.apache.org>
X-Original-To: apmail-hadoop-mapreduce-dev-archive@minotaur.apache.org
Delivered-To: apmail-hadoop-mapreduce-dev-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id C6880D1D3
	for <apmail-hadoop-mapreduce-dev-archive@minotaur.apache.org>;
 Fri, 28 Sep 2012 04:39:20 +0000 (UTC)
Received: (qmail 30934 invoked by uid 500); 28 Sep 2012 04:39:19 -0000
Delivered-To: apmail-hadoop-mapreduce-dev-archive@hadoop.apache.org
Received: (qmail 30275 invoked by uid 500); 28 Sep 2012 04:39:19 -0000
Mailing-List: contact mapreduce-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:mapreduce-dev-help@hadoop.apache.org>
List-Unsubscribe: <mailto:mapreduce-dev-unsubscribe@hadoop.apache.org>
List-Post: <mailto:mapreduce-dev@hadoop.apache.org>
List-Id: <mapreduce-dev.hadoop.apache.org>
Reply-To: mapreduce-dev@hadoop.apache.org
Delivered-To: mailing list mapreduce-dev@hadoop.apache.org
Received: (qmail 30247 invoked by uid 99); 28 Sep 2012 04:39:18 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Sep 2012 04:39:18 +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 (athena.apache.org: domain of yhemanth@gmail.com designates
 209.85.212.176 as permitted sender)
Received: from [209.85.212.176] (HELO mail-wi0-f176.google.com)
 (209.85.212.176)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Sep 2012 04:39:11 +0000
Received: by wibhn14 with SMTP id hn14so927003wib.11
        for <multiple recipients>; Thu, 27 Sep 2012 21:38:50 -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
         :cc:content-type:content-transfer-encoding;
        bh=jw6Jxwziu7TuLQ7BwMNMhoo727ztCpJpnQGCb4LPK9Y=;
        b=Ds/zx6vcVn1Q9ZN59NUZ9bQFltfXRx0WoRvuUkEjDJX5XlWzKfncqO7bQxRXwqz88D
         y37/VOyTRNkTDZVPXB/FLJ6qaPcRYRgjRVeCm2V8iedyRBhfKGDzStify/E9wYoGrsNP
         IiyTJTLamLwCqLSU0AJH7kiycWJ7qqUqP8apsus7hRjTAMZnI8Cmd8XFylGlAXn+1YoC
         nFgBhofBk03yNKqgExYbQN9jBFjvW/ImXERwTrJzH7fnFf2tPjvbt1XyJQ4RA4F2zydh
         1wLAPodzSBMtS0PuuTWA2fk40OCipvCxwgKe+iDSOrf4eFzpDGMIbDdWOBCzlzjJm9Fz
         aKUw==
MIME-Version: 1.0
Received: by 10.180.33.111 with SMTP id q15mr1106734wii.20.1348807130350; Thu,
 27 Sep 2012 21:38:50 -0700 (PDT)
Received: by 10.223.155.9 with HTTP; Thu, 27 Sep 2012 21:38:50 -0700 (PDT)
In-Reply-To: 
 <CACD21EOkH6Q5nRdVo1oJ5nhmMv43GBncXkUKcPhaqzJQNDcEbg@mail.gmail.com>
References: 
 <CAJ8VZfVnUg4ZotyNEjafyQoy7kmthEatSJmM4pbh5PiGa7vyhg@mail.gmail.com>
	<CACD21EOkH6Q5nRdVo1oJ5nhmMv43GBncXkUKcPhaqzJQNDcEbg@mail.gmail.com>
Date: Fri, 28 Sep 2012 10:08:50 +0530
Message-ID: 
 <CA++OR+ofdhTB83jQFCrdu=WqpVEPck33ZA3TMrb4rYzEagwzug@mail.gmail.com>
Subject: Re: How not to clean MapReduce temp data?
From: Hemanth Yamijala <yhemanth@gmail.com>
To: mapreduce-user@hadoop.apache.org
Cc: mapreduce-dev@hadoop.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Virus-Checked: Checked by ClamAV on apache.org

Adding to Bejoy's response, if you want to just keep the temp output
of failed tasks, you can also use keep.failed.task.files.

Also, these config variable names are as per Hadoop 1.0. In trunk,
they are called mapreduce.task.files.preserve.filepattern and
mapreduce.task.files.preserve.failedtasks respectively.

Thanks
Hemanth

On Thu, Sep 27, 2012 at 11:18 PM, Bejoy Ks <bejoy.hadoop@gmail.com> wrote:
> Hi
>
> The temporary output from tasks can be preserved using the following
> property'keep.task.files.pattern'
>
> http://books.google.co.in/books?id=3DdrbI_aro20oC&pg=3DPA178&lpg=3DPA178&=
dq=3Dkeep.task.files.pattern&source=3Dbl&ots=3DtZAmxgm_j4&sig=3DGuc0bh2BQzl=
bMqOADtic5WciIz0&hl=3Den&sa=3DX&ei=3DzI9kULbDM8zhrAe3jYH4BA&ved=3D0CFoQ6AEw=
Bg#v=3Donepage&q=3Dkeep.task.files.pattern&f=3Dfalse
>
>
> On Thu, Sep 27, 2012 at 10:49 PM, Pedro S=E1 da Costa <psdc1978@gmail.com=
>
> wrote:
>>
>> Hi,
>>
>> Is there a parameter to avoid to clean the temporary data created during
>> the job execution after the job end?
>>
>> --
>> Best regards,
>>
>