hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-3992) Reduce fetcher doesn't verify HTTP status code of response
Date Sat, 24 Mar 2012 14:58:26 GMT

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

Steve Loughran commented on MAPREDUCE-3992:
-------------------------------------------

+1 for the patch for branch-1 too.
                
> Reduce fetcher doesn't verify HTTP status code of response
> ----------------------------------------------------------
>
>                 Key: MAPREDUCE-3992
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3992
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv1
>    Affects Versions: 0.23.1, 0.24.0, 1.0.1
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>             Fix For: 0.24.0, 0.23.3
>
>         Attachments: mr-3992-branch-1.txt, mr-3992.txt
>
>
> Currently, the reduce fetch code doesn't check the HTTP status code of the response.
This can lead to the following situation:
> - the map output servlet gets an IOException after setting the headers but before the
first call to flush()
> - this causes it to send a response with a non-OK result code, including the exception
text as the response body (response.sendError() does this if the response isn't committed)
> - it will still include the response headers indicating it's a valid response
> In the case of a merge-to-memory, the compression codec might then try to interpret the
HTML response as compressed data, resulting in either a huge allocation (OOME) or some other
nasty error. This bug seems to be present in MR1, but haven't checked trunk/MR2 yet.

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

        

Mime
View raw message