You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2015/05/06 05:28:09 UTC

[jira] [Updated] (MAPREDUCE-4919) All maps hangs when set mapreduce.task.io.sort.factor to 1

     [ https://issues.apache.org/jira/browse/MAPREDUCE-4919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Allen Wittenauer updated MAPREDUCE-4919:
----------------------------------------
    Labels: BB2015-05-TBR  (was: )

> All maps hangs when set mapreduce.task.io.sort.factor to 1
> ----------------------------------------------------------
>
>                 Key: MAPREDUCE-4919
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4919
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: client
>            Reporter: Jerry Chen
>            Assignee: Jerry Chen
>              Labels: BB2015-05-TBR
>         Attachments: MAPREDUCE-4919.patch
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> In one of my testing that when I set mapreduce.task.io.sort.factor to 1, all the maps hang and will never end. But the CPU usage for each node are very high and until killed by the app master when time out comes, and the job failed. 
> I traced the problem and found out that all the maps hangs on the final merge phase.
> The while loop in computeBytesInMerges will never end with a factor of 1:
> int f = 1; //in my case
> int n = 16; //in my case
> while (n > f || considerFinalMerge) {
>   ...
>   n -= (f-1);
>   f = factor;
> }
> As the f-1 will equals 0 and n will always be 16 and the while runs for ever.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)