Return-Path: X-Original-To: apmail-hadoop-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-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 70026105FE for ; Sun, 20 Oct 2013 16:49:45 +0000 (UTC) Received: (qmail 8866 invoked by uid 500); 20 Oct 2013 16:49:38 -0000 Delivered-To: apmail-hadoop-user-archive@hadoop.apache.org Received: (qmail 8623 invoked by uid 500); 20 Oct 2013 16:49:32 -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 8610 invoked by uid 99); 20 Oct 2013 16:49:31 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 20 Oct 2013 16:49:31 +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.171 as permitted sender) Received: from [209.85.223.171] (HELO mail-ie0-f171.google.com) (209.85.223.171) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 20 Oct 2013 16:49:25 +0000 Received: by mail-ie0-f171.google.com with SMTP id tp5so10124495ieb.30 for ; Sun, 20 Oct 2013 09:49:04 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=KNBULsaqsxSZZ2b3Xx+VjgnhEz/cJKiSnsiNFJBe5nE=; b=IIYnCbYE8ljMZX4lLicKOOMmbzXr1RYX7C8Qq2y5HR6zS/utuv9UFNOKfn82WWjl9Z Ml0PexhyTYSLqdUxZxK/wB1XkkorztokMUshR4eaB4I0CK8OtPFrAgjzeqgY0OBh3USW ek/fNPVamwfkMSKx1DD7CMehzfuKzy3+fpkQX9GPKvLJ6yf2g9IiP5g/Sre+6BGmZuJL 7PIMfvMc5Psho9m+5MhxSYRghlVFOkoXhgdJF/60embo7p/DUp9oRCBsREDidajHeCsC GSIk/GKogTRhDJT3Oro+d0/SLaKnbl2YEUayFSGtOdf0OyaRgYBSpQph1jIyAJfcdSOP sEgA== X-Gm-Message-State: ALoCoQlc9RXJDnVqPbMYH0WuAUIMQh9R17dGT0l5BQ/ERpJ32+eVTFdN8fx5sKwU1Uj5XftxhLlG X-Received: by 10.50.225.3 with SMTP id rg3mr6717804igc.28.1382287744220; Sun, 20 Oct 2013 09:49:04 -0700 (PDT) MIME-Version: 1.0 Received: by 10.50.234.225 with HTTP; Sun, 20 Oct 2013 09:48:44 -0700 (PDT) In-Reply-To: <869970D71E26D7498BDAC4E1CA92226B86D8A0DB@MBX021-E3-NJ-2.exch021.domain.local> References: <869970D71E26D7498BDAC4E1CA92226B86D8A0DB@MBX021-E3-NJ-2.exch021.domain.local> From: Harsh J Date: Sun, 20 Oct 2013 22:18:44 +0530 Message-ID: Subject: Re: temporary file locations for YARN applications To: "" Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org Every container gets its own local work directory (You can use the relative ./) thats auto-cleaned up at the end of the container's life. This is the best place to store the temporary files. This is not something you need custom configuration for. Do the files need to be on a distributed FS or a local one? On Sun, Oct 20, 2013 at 8:54 PM, John Lilley wrote: > We have a pure YARN application (no MapReduce) that has need to store a > significant amount of temporary data. How can we know the best location for > these files? How can we ensure that our YARN tasks have write access to > these locations? Is this something that must be configured outside of YARN? > > Thanks, > > John > > > > -- Harsh J