hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wangda Tan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-6302) Preempt reducers after a configurable timeout irrespective of headroom
Date Fri, 16 Oct 2015 17:27:08 GMT

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

Wangda Tan commented on MAPREDUCE-6302:

+1 to backport this issue to 2.6.x and 2.7.x

> Preempt reducers after a configurable timeout irrespective of headroom
> ----------------------------------------------------------------------
>                 Key: MAPREDUCE-6302
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6302
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>    Affects Versions: 2.6.0
>            Reporter: mai shurong
>            Assignee: Karthik Kambatla
>            Priority: Critical
>             Fix For: 2.8.0
>         Attachments: AM_log_head100000.txt.gz, AM_log_tail100000.txt.gz, log.txt, mr-6302-1.patch,
mr-6302-2.patch, mr-6302-3.patch, mr-6302-4.patch, mr-6302-5.patch, mr-6302-6.patch, mr-6302-7.patch,
mr-6302-prelim.patch, mr-6302_branch-2.patch, queue_with_max163cores.png, queue_with_max263cores.png,
> I submit a  big job, which has 500 maps and 350 reduce, to a queue(fairscheduler) with
300 max cores. When the big mapreduce job is running 100% maps, the 300 reduces have occupied
300 max cores in the queue. And then, a map fails and retry, waiting for a core, while the
300 reduces are waiting for failed map to finish. So a deadlock occur. As a result, the job
is blocked, and the later job in the queue cannot run because no available cores in the queue.
> I think there is the similar issue for memory of a queue .

This message was sent by Atlassian JIRA

View raw message