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 9590810C34 for ; Tue, 7 May 2013 07:45:41 +0000 (UTC) Received: (qmail 421 invoked by uid 500); 7 May 2013 07:45:22 -0000 Delivered-To: apmail-hadoop-mapreduce-user-archive@hadoop.apache.org Received: (qmail 99627 invoked by uid 500); 7 May 2013 07:45:18 -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 99571 invoked by uid 99); 7 May 2013 07:45:17 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 May 2013 07:45:17 +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.172 as permitted sender) Received: from [209.85.223.172] (HELO mail-ie0-f172.google.com) (209.85.223.172) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 May 2013 07:45:11 +0000 Received: by mail-ie0-f172.google.com with SMTP id 16so411313iea.3 for ; Tue, 07 May 2013 00:44:50 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:content-transfer-encoding :x-gm-message-state; bh=J0Nq8qok4tj2V4e9JbzYNqB2JR9ZPeeOJfCKoK99/ew=; b=o/g+HCQwZsW4aJZ1pJdFg6/JOTxC8sRP2SLkWaWyJsMSRmP2OPCNY5MWJPI8N5SXRq j/xJREaXDcL6BgnQNPlT0omdPEggr7dWj/mLHL0JUdd4FZJqHrTdgf3OasWCWdCWcR4V mqw+1U1TQ1XEhN4FnS1BwLrjNfrC+wtVoU4CixyFjRh3TK/qelHfg+Q/3ovZbUJI+MRu UD822JBNkD9jUjZKedlHmKfvYl5PKVJlcTJ0HBoljiGojkGH5oK+h/QRG05Rx6nRSerN o5joaVYCv5145B9729u3IupeQstYtIQGXCEDIZN0dmMKuLQCOgwIoVCkr4mO0VxHGPFn cHaQ== X-Received: by 10.50.88.103 with SMTP id bf7mr3755030igb.9.1367912690782; Tue, 07 May 2013 00:44:50 -0700 (PDT) MIME-Version: 1.0 Received: by 10.50.101.77 with HTTP; Tue, 7 May 2013 00:44:30 -0700 (PDT) In-Reply-To: <1367850274.24846.YahooMailNeo@web125601.mail.ne1.yahoo.com> References: <1367850274.24846.YahooMailNeo@web125601.mail.ne1.yahoo.com> From: Harsh J Date: Tue, 7 May 2013 13:14:30 +0530 Message-ID: Subject: Re: no _SUCCESS file in MR output directory. To: "user@oozie.apache.org" , Eduardo Afonso Ferreira Cc: "user@hadoop.apache.org" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Gm-Message-State: ALoCoQlXbfGiwn+xVJXjUSn2lOFKf2op/VmEWKdjKBNPNXbnyxj++PjQkal8ps6cBaLlKkG7p85z X-Virus-Checked: Checked by ClamAV on apache.org Good observance: Pig does seem to use a default "false" when possible, to disable the _SUCCESS creation. I don't see Hive do that, nor any part of the stock Apache Hadoop MR jobs. Rahul - Do you use a Pig action in your WF? Also, are you definitively seeing _SUCCESS being created after you add the option manually? On Mon, May 6, 2013 at 7:54 PM, Eduardo Afonso Ferreira wrote: > I'm not sure if Pig disables it or not, but I remember I had issues when = that file was to be created by the MR jobs due to the fact of Oozie or Pig = removing temporary directories or something like that. I remember seeing an= exception about failure to create the SUCCESS file, so I started using the= following property in my workflow pig action to disable that: > > > ... > > > > mapreduce.fileoutputcommitter.marksuccessfuljob= s > false > > ... > > ... > > > > > ________________________________ > From: Rahul Bhattacharjee > To: "user@hadoop.apache.org" ; user@oozie.apache.= org > Sent: Monday, May 6, 2013 3:48 AM > Subject: Re: no _SUCCESS file in MR output directory. > > > I wanted to confirm whether oozie disables the _SUCCESS file creation whe= n > it triggers a MR job. > > I am triggering a MR job (actually a bunch of 'em) from oozie and the > workflow completes successfully , however I do not see any kind of _SUCCE= SS > file in the output directory. > When I set the file output committer's configuration > (mapreduce.fileoutputcommitter. > marksuccessfuljobs > ) to true.It generates the success file. Wanted to confirm if oozie does > the disabling of success file creation. > > Thanks, > Rahul > > > On Mon, May 6, 2013 at 12:34 PM, Rahul Bhattacharjee < > rahul.rec.dgp@gmail.com> wrote: > >> Oozie is being used for triggering the MR job. Looks like oozie disables >> the success file creation using the configuration that you have mentione= d >> for FileOutputCommitter. >> >> I have enabled it by setting this property in conf. >> >> Rahul >> >> >> On Mon, May 6, 2013 at 9:38 AM, Rahul Bhattacharjee < >> rahul.rec.dgp@gmail.com> wrote: >> >>> Thanks Harsh for the pointers. I will find out more on this. >>> >>> >>> On Sun, May 5, 2013 at 11:26 PM, Harsh J wrote: >>> >>>> I can think of a few, most obvious ones: >>>> >>>> 1. Job didn't succeed and/or the file was deleted (*shields self*) >>>> 2. Job overrode the default FileOutputCommitter with something that >>>> doesn't do success marking. >>>> 3. Job specifically asked to not create such files, via config >>>> mapreduce.fileoutputcommitter.marksuccessfuljobs or so, set to false. >>>> >>>> On Sun, May 5, 2013 at 9:54 PM, Rahul Bhattacharjee >>>> wrote: >>>> > Hi, >>>> > >>>> > >>>> > A few days back , I was going through a MR job's output , but there >>>> wasn't >>>> > any _SUCCESS file in the output directory. >>>> > I was wondering what all reasons for this (no _SUCCESS file)? >>>> > >>>> > Thanks, >>>> > Rahul >>>> >>>> >>>> >>>> -- >>>> Harsh J >>>> >>> >>> >> --=20 Harsh J