[
https://issues.apache.org/jira/browse/HADOOP-4716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12656605#action_12656605
]
Amar Kamat commented on HADOOP-4716:
------------------------------------
Looks like HADOOP-4683 solves this issue for now. The way HADOOP-4683 solves
this issue is that it fetches all the events in one go and latest events are
fetched faster. So the fact that a map location is faulty/missing is
immediately passed onto the reducer which adds the map output location to the
_ignore list_. I couldn't reproduce this bug with trunk. Also HADOOP-4220 tries
to reduce the run-time of this testcase.
> testRestartWithLostTracker frequently times out
> -----------------------------------------------
>
> Key: HADOOP-4716
> URL: https://issues.apache.org/jira/browse/HADOOP-4716
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Reporter: Johan Oskarsson
> Assignee: Amar Kamat
> Priority: Blocker
> Fix For: 0.20.0
>
> Attachments: HADOOP-4716-v1.patch, log.txt
>
>
> This test frequently times out:
> org.apache.hadoop.mapred.TestJobTrackerRestartWithLostTracker.testRestartWithLostTracker
> Example:
> http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3637/testReport/org.apache.hadoop.mapred/TestJobTrackerRestartWithLostTracker/testRestartWithLostTracker/
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
