hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-6541) Exclude scheduled reducer memory when calculating available mapper slots from headroom to avoid deadlock
Date Thu, 27 Oct 2016 13:01:03 GMT

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

Hudson commented on MAPREDUCE-6541:

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #10703 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/10703/])
MAPREDUCE-6541. Exclude scheduled reducer memory when calculating (naganarasimha_gr: rev 060558c6f221ded0b014189d5b82eee4cc7b576b)
* (edit) hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/test/java/org/apache/hadoop/mapreduce/v2/app/rm/TestRMContainerAllocator.java
* (edit) hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/rm/RMContainerAllocator.java

> Exclude scheduled reducer memory when calculating available mapper slots from headroom
to avoid deadlock 
> ---------------------------------------------------------------------------------------------------------
>                 Key: MAPREDUCE-6541
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6541
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>    Affects Versions: 2.7.1
>            Reporter: Wangda Tan
>            Assignee: Varun Saxena
>             Fix For: 2.8.0, 2.9.0, 3.0.0-alpha2
>         Attachments: MAPREDUCE-6541.01.patch, MAPREDUCE-6541.02.patch
> We saw a MR deadlock recently:
> - When NM restarted by framework without enable recovery, containers running on these
nodes will be identified as "ABORTED", and MR AM will try to reschedule "ABORTED" mapper containers.
> - Since such lost mappers are "ABORTED" container, MR AM gives normal mapper priority
(priority=20) to such mapper requests. If there's any pending reducer (priority=10) at the
same time, mapper requests need to wait for reducer requests satisfied.
> - In our test, one mapper needs 700+ MB, reducer needs 1000+ MB, and RM available resource
= mapper-request = (700+ MB), only one job was running in the system so scheduler cannot allocate
more reducer containers AND MR-AM thinks there're enough headroom for mapper so reducer containers
will not be preempted.
> MAPREDUCE-6302 can solve most of the problems, but in the other hand, I think we may
need to exclude scheduled reducers resource when calculating #available-mapper-slots from
headroom. Which we can avoid excessive reducer preemption.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: mapreduce-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-help@hadoop.apache.org

View raw message