[
https://issues.apache.org/jira/browse/MAPREDUCE-4146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13295430#comment-13295430
]
Jim Donofrio commented on MAPREDUCE-4146:
-----------------------------------------
Hadoop 2.0.1-alpha
{code}
if (locations.length > maxBlockLocations) {
throw new IOException("Max block location exceeded for split: "
+ split + " splitsize: " + locations.length +
" maxsize: " + maxBlockLocations);
}
{code}
Hadoop 1.0.3
I am wondering why this part of the path conflicts with the current behavior in
Hadoop 1.0.3 by failing thejob with an IOException instead of just capping the
number of splits? It is common to exceed the split number when doing a map side
join
> Support limits on task status string length and number of block locations in
> branch-2
> -------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-4146
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4146
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Reporter: Tom White
> Assignee: Ahmed Radwan
> Fix For: 2.0.1-alpha
>
> Attachments: MAPREDUCE-4146.patch, MAPREDUCE-4146_rev2.patch
>
>
> This brings MAPREDUCE-1943 to branch-2. Counter limits were introduced in
> MAPREDUCE-901.
--
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
