Return-Path: X-Original-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 57D1D96D3 for ; Tue, 11 Sep 2012 14:17:08 +0000 (UTC) Received: (qmail 6646 invoked by uid 500); 11 Sep 2012 14:17:08 -0000 Delivered-To: apmail-hadoop-mapreduce-issues-archive@hadoop.apache.org Received: (qmail 6612 invoked by uid 500); 11 Sep 2012 14:17:08 -0000 Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: mapreduce-issues@hadoop.apache.org Delivered-To: mailing list mapreduce-issues@hadoop.apache.org Received: (qmail 6604 invoked by uid 99); 11 Sep 2012 14:17:08 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Sep 2012 14:17:08 +0000 Date: Wed, 12 Sep 2012 01:17:08 +1100 (NCT) From: "Hudson (JIRA)" To: mapreduce-issues@hadoop.apache.org Message-ID: <762820805.63549.1347373028137.JavaMail.jiratomcat@arcas> Subject: [jira] [Commented] (MAPREDUCE-4607) Race condition in ReduceTask completion can result in Task being incorrectly failed MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/MAPREDUCE-4607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13453046#comment-13453046 ] Hudson commented on MAPREDUCE-4607: ----------------------------------- Integrated in Hadoop-Common-trunk-Commit #2716 (See [https://builds.apache.org/job/Hadoop-Common-trunk-Commit/2716/]) Update CHANGES.txt for MAPREDUCE-4607 commit. (Revision 1383423) MAPREDUCE-4607. Race condition in ReduceTask completion can result in Task being incorrectly failed. Contributed by Bikas Saha. (Revision 1383422) Result = SUCCESS tomwhite : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1383423 Files : * /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt tomwhite : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1383422 Files : * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/job/impl/TaskAttemptImpl.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/job/impl/TaskImpl.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/test/java/org/apache/hadoop/mapreduce/v2/app/TestMRApp.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/test/java/org/apache/hadoop/mapreduce/v2/app/job/impl/TestTaskImpl.java > Race condition in ReduceTask completion can result in Task being incorrectly failed > ----------------------------------------------------------------------------------- > > Key: MAPREDUCE-4607 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-4607 > Project: Hadoop Map/Reduce > Issue Type: Bug > Affects Versions: 2.0.0-alpha > Reporter: Bikas Saha > Assignee: Bikas Saha > Fix For: 2.0.3-alpha > > Attachments: MAPREDUCE-4607.1.patch, MAPREDUCE-4607.2.patch, MAPREDUCE-4607.3.patch, MAPREDUCE-4607.4.patch, MAPREDUCE-4607.patch > > > Problem reported by chackaravarthy in MAPREDUCE-4252 > This problem has been handled when speculative task launched for map task and other attempt got failed (not killed) > Can the similar kind of scenario can happen in case of reduce task? > Consider the following scenario for reduce task in case of speculation (one attempt got killed): > 1. A task attempt is started. > 2. A speculative task attempt for the same task is started. > 3. The first task attempt completes and causes the task to transition to SUCCEEDED. > 4. Then speculative task attempt will be killed because of the completion of first attempt. > As a result, internal error will be thrown from this attempt (TaskImpl.MapRetroactiveKilledTransition) and hence task attempt failure leads to job failure. > TaskImpl.MapRetroactiveKilledTransition > if (!TaskType.MAP.equals(task.getType())) { > LOG.error("Unexpected event for REDUCE task " + event.getType()); > task.internalError(event.getType()); > } > So, do we need to have following code in MapRetroactiveKilledTransition also just like in MapRetroactiveFailureTransition. > if (event instanceof TaskTAttemptEvent) { > TaskTAttemptEvent castEvent = (TaskTAttemptEvent) event; > if (task.getState() == TaskState.SUCCEEDED && > !castEvent.getTaskAttemptID().equals(task.successfulAttempt)) { > // don't allow a different task attempt to override a previous > // succeeded state > return TaskState.SUCCEEDED; > } > } > please check whether this is a valid case and give your suggestion. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira