[ https://issues.apache.org/jira/browse/MAPREDUCE-5570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13936220#comment-13936220 ]
Hudson commented on MAPREDUCE-5570: ----------------------------------- SUCCESS: Integrated in Hadoop-Mapreduce-trunk #1727 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1727/]) MAPREDUCE-5570. Map task attempt with fetch failure has incorrect attempt finish time. Contributed by Rushabh S Shah (jlowe: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1577692) * /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt * /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/test/java/org/apache/hadoop/mapreduce/v2/app/job/impl/TestTaskAttempt.java > Map task attempt with fetch failure has incorrect attempt finish time > --------------------------------------------------------------------- > > Key: MAPREDUCE-5570 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-5570 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: mr-am, mrv2 > Affects Versions: 0.23.9, 2.1.1-beta > Reporter: Jason Lowe > Assignee: Rushabh S Shah > Fix For: 2.4.0 > > Attachments: patch-MapReduce-5570-v2.patch, patch-MapReduce-5570.patch > > > If a map task attempt is retroactively failed due to excessive fetch failures > reported by reducers then the attempt's finish time is set to the time the > task was retroactively failed rather than when the task attempt completed. > This causes the map task attempt to appear to have run for much longer than > it actually did. -- This message was sent by Atlassian JIRA (v6.2#6252)