[ 
https://issues.apache.org/jira/browse/MAPREDUCE-4423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13419844#comment-13419844
 ] 

Hudson commented on MAPREDUCE-4423:
-----------------------------------

Integrated in Hadoop-Mapreduce-trunk #1143 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1143/])
    svn merge --change -1363454 for reverting MAPREDUCE-4423 (Revision 1363935)

     Result = FAILURE
tgraves : 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1363935
Files : 
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapreduce/task/reduce/Fetcher.java
* 
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/test/java/org/apache/hadoop/mapreduce/task/reduce/TestFetcher.java

                
> Potential infinite fetching of map output
> -----------------------------------------
>
>                 Key: MAPREDUCE-4423
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4423
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>    Affects Versions: 0.23.3, 2.1.0-alpha, 3.0.0
>            Reporter: Robert Joseph Evans
>            Assignee: Robert Joseph Evans
>            Priority: Critical
>             Fix For: 0.23.3, 3.0.0, 2.2.0-alpha
>
>         Attachments: MR-4423.txt, MR-4423.txt
>
>
> Inside Fetcher.java there are a few cases where an error can happen and the 
> corresponding map task is not marked as a fetch failure.  One of these is if 
> the Shuffle server returns a malformed result.
> MAPREDUCE-3992 makes this case a lot less common, but it is still possible.  
> IF the shuffle handler always returns a malformed result, but a OK response 
> the Fetcher will never stop trying to fetch those results. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to