Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Thu, 12 Nov 2015 14:22:11 +0000 (UTC)
From: "Varun Saxena (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: <JIRA.12911221.1446846434000.50120.1447338131031@Atlassian.JIRA>
In-Reply-To: <JIRA.12911221.1446846434000@Atlassian.JIRA>
References: <JIRA.12911221.1446846434000@Atlassian.JIRA>
 <JIRA.12911221.1446846434900@arcas>
Subject: [jira] [Updated] (MAPREDUCE-6541) Exclude scheduled reducer memory
 when calculating available mapper slots from headroom to avoid deadlock
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Varun Saxena updated MAPREDUCE-6541:
------------------------------------
    Affects Version/s: 2.7.1
     Target Version/s: 2.7.3
               Status: Patch Available  (was: Open)

> 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
>         Attachments: MAPREDUCE-6541.01.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
(v6.3.4#6332)