[
https://issues.apache.org/jira/browse/MAPREDUCE-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13158247#comment-13158247
]
Bhallamudi Venkata Siva Kamesh commented on MAPREDUCE-3423:
-----------------------------------------------------------
bq.Am not sure I get the changes in the second part of the patch:
I updated this part, thinking mapid won't be null, handling this in the first
part and returning false in the error scenarios.This exception happens when
MergeManager tries to allocate location for the map output,so, logging the
same.
> Fetcher Thread should log proper exception
> ------------------------------------------
>
> Key: MAPREDUCE-3423
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3423
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 0.24.0
> Reporter: Bhallamudi Venkata Siva Kamesh
> Attachments: MAPREDUCE-3423.patch
>
>
> Exception should be logged properly when there is any while deserializing
> Shuffle Header information .
> {code}
> if (mapId == null || mapOutput == null) {
> LOG.info("fetcher#" + id + " failed to read map header" +
> mapId + " decomp: " +
> decompressedLength + ", " + compressedLength, ioe);
> return false;
> }
> {code}
--
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
