Return-Path: Delivered-To: apmail-hadoop-common-user-archive@www.apache.org Received: (qmail 41597 invoked from network); 16 Sep 2010 20:34:31 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 16 Sep 2010 20:34:31 -0000 Received: (qmail 35461 invoked by uid 500); 16 Sep 2010 20:34:29 -0000 Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org Received: (qmail 35420 invoked by uid 500); 16 Sep 2010 20:34:29 -0000 Mailing-List: contact common-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-user@hadoop.apache.org Delivered-To: mailing list common-user@hadoop.apache.org Received: (qmail 35412 invoked by uid 99); 16 Sep 2010 20:34:28 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Sep 2010 20:34:28 +0000 X-ASF-Spam-Status: No, hits=0.7 required=10.0 tests=RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [66.196.96.80] (HELO smtp104.sbc.mail.re3.yahoo.com) (66.196.96.80) by apache.org (qpsmtpd/0.29) with SMTP; Thu, 16 Sep 2010 20:34:21 +0000 Received: (qmail 80764 invoked from network); 16 Sep 2010 20:34:00 -0000 Received: from [10.0.1.4] (Schmed@75.45.107.156 with login) by smtp104.sbc.mail.re3.yahoo.com with SMTP; 16 Sep 2010 13:33:59 -0700 PDT X-Yahoo-SMTP: W4QmOr6swBCBPg1ENP5AT7BtGajFo9o- X-YMail-OSG: cKv3xBMVM1kg8vJyuIsVY_8kQ28K0LvvviHWrux5TGXQIl. Jz2wbacOIDx2nn2N1u9BDid8qRV69YuV_uyNUP2oVo0X5tGBvaJSPJ0nJFZh nOK6vMBO7Zq1cb5QeZU4F8DkOXTh2HvygDmxw53PHdXGpVUx47BVVLmlX8lP R_On.9Ycs9NuU1Uq2IH_.7fqVFGRYzWJLZFBOzUz7mH5j4SOMYWhYZL7tWWO JuADFlbBip1r9SZzhJaNq.vevUtusOpPjBi5SB3O27wDeBYkPeWb4FsiROZB wgzaa6tl557v3No5yIASjHKwqJgpKdVwUjheqe6EiyJtN8Xei5NPDGHjc.w6 HNfpxB_bRJKNq7Qf6Pwd9BiK1uCF9GM_5j1gDd6nQUugE7t2_wh6G_cJn4Wb suMapko0d6yoUmgxnEoHGTbcqSzkmEg4V4fSn2e5KdrnkfZTX3D.XsyUd6w- - X-Yahoo-Newman-Property: ymail-3 Mime-Version: 1.0 Message-Id: In-Reply-To: References: Date: Thu, 16 Sep 2010 13:33:48 -0700 To: common-user@hadoop.apache.org From: Chris Schneider Subject: Re: Getting past a HADOOP-5233 issue? Content-Type: text/plain; charset="us-ascii" X-Virus-Checked: Checked by ClamAV on apache.org Hi Gang, >I'm running 0.19.1, and unfortunately I've apparently just been bitten by https://issues.apache.org/jira/browse/HADOOP-5233. (Note: I usually run 0.19.2 and will soon be running on 0.20.2, but had trouble finding a public m1.large AMI for Amazon EC2.) > >My map-only job has written 22971 parts (of 22972) to my output sequence file in DFS. I'm wondering whether anyone has a good idea for unsticking this map task by hand so that (ideally) it will write its output to the sequence file and I can move on. It wouldn't be the end of the world to kill the job and go on without this output, but I thought I'd ask first in case someone had a good idea. Just in case anyone else has a similar problem, I happened across this command just before I was about to kill my job: hadoop job [-fail-task ] I was able to fail the offending task (specifying the task attempt ID, of course - see https://issues.apache.org/jira/browse/MAPREDUCE-985), a new attempt was immediately launched, and the job completed successfully. Hooray! FYI, - Chris -- ---------------------------- Chris Schneider Bixo Labs, Inc. http://www.bixolabs.com CSchneider@Mail.BixoLabs.com ----------------------------