Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Tue, 12 Mar 2013 19:51:14 +0000 (UTC)
From: "Robert Joseph Evans (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: <JIRA.12636642.1363117479377.428060.1363117874130@arcas>
In-Reply-To: <JIRA.12636642.1363117479377@arcas>
References: <JIRA.12636642.1363117479377@arcas>
Subject: [jira] [Updated] (MAPREDUCE-5060) Fetch failures that time out only
 count against the first map task
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Robert Joseph Evans updated MAPREDUCE-5060:
-------------------------------------------

    Status: Patch Available  (was: Open)
    
> Fetch failures that time out only count against the first map task
> ------------------------------------------------------------------
>
>                 Key: MAPREDUCE-5060
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5060
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>            Reporter: Robert Joseph Evans
>            Assignee: Robert Joseph Evans
>            Priority: Critical
>         Attachments: MR-5060.txt
>
>
> When a fetch failure happens, if the socket has already "connected" it is only counted against the first map task.  But most of the time it is because of an issue with the Node itself, not the individual map task, and as such all failures when trying to initiate the connection should count against all of the tasks.
> This caused a particularly unfortunate job to take an hour an a half longer then it needed to.

--
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