Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <1267878054.1208538263662.JavaMail.jira@brutus>
Date: Fri, 18 Apr 2008 10:04:23 -0700 (PDT)
From: "Devaraj Das (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Updated: (HADOOP-3279) TaskTracker should check for
 SUCCEEDED task status in addition to COMMIT_PENDING status when it fails
 maps due to lost map outputs
In-Reply-To: <1548499824.1208538263433.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HADOOP-3279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Devaraj Das updated HADOOP-3279:
--------------------------------

    Attachment: 3279.patch

Straightforward patch..

> TaskTracker should check for SUCCEEDED task status in addition to COMMIT_PENDING status when it fails maps due to lost map outputs
> ----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-3279
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3279
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.17.0
>            Reporter: Devaraj Das
>            Assignee: Devaraj Das
>            Priority: Blocker
>             Fix For: 0.17.0
>
>         Attachments: 3279.patch
>
>
> Post HADOOP-3140, tasks could be marked as SUCCEEDED by the TaskTracker. Hence, the TaskTracker should check for SUCCEEDED task status in addition to COMMIT_PENDING status when it fails maps due to lost map outputs

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.