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 "PengZhang (JIRA)" <ji...@apache.org> on 2013/06/02 15:23:20 UTC

[jira] [Commented] (MAPREDUCE-5279) mapreduce scheduling deadlock

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

PengZhang commented on MAPREDUCE-5279:
--------------------------------------

Any suggestions for this patch?
I've done some tests on our cluster, and found the job that always got dead lock works well now.
                
> mapreduce scheduling deadlock
> -----------------------------
>
>                 Key: MAPREDUCE-5279
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5279
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2, scheduler
>    Affects Versions: 2.0.3-alpha
>            Reporter: PengZhang
>             Fix For: trunk
>
>         Attachments: MAPREDUCE-5279.patch, MAPREDUCE-5279-v2.patch
>
>
> YARN-2 imported cpu dimension scheduling, but MR RMContainerAllocator doesn't take into account virtual cores while scheduling reduce tasks.
> This may cause more reduce tasks to be scheduled because memory is enough. And on a small cluster, this will end with deadlock, all running containers are reduce tasks but map phase is not finished. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira