Return-Path: X-Original-To: apmail-hadoop-mapreduce-dev-archive@minotaur.apache.org Delivered-To: apmail-hadoop-mapreduce-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 671F070F7 for ; Sat, 16 Jul 2011 22:14:25 +0000 (UTC) Received: (qmail 5687 invoked by uid 500); 16 Jul 2011 22:14:24 -0000 Delivered-To: apmail-hadoop-mapreduce-dev-archive@hadoop.apache.org Received: (qmail 5379 invoked by uid 500); 16 Jul 2011 22:14:23 -0000 Mailing-List: contact mapreduce-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: mapreduce-dev@hadoop.apache.org Delivered-To: mailing list mapreduce-dev@hadoop.apache.org Received: (qmail 5363 invoked by uid 99); 16 Jul 2011 22:14:23 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 16 Jul 2011 22:14:23 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 16 Jul 2011 22:14:21 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id DFE5D835AC for ; Sat, 16 Jul 2011 22:13:59 +0000 (UTC) Date: Sat, 16 Jul 2011 22:13:59 +0000 (UTC) From: "Arun C Murthy (JIRA)" To: mapreduce-dev@hadoop.apache.org Message-ID: <256722318.20434.1310854439914.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <1353413269.19066.1310769600008.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Resolved] (MAPREDUCE-2694) AM releases too many containers due to the protocol MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/MAPREDUCE-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy resolved MAPREDUCE-2694. -------------------------------------- Resolution: Not A Problem I thought more about this... I've spent time on this in the beginning and I don't think a delta protocol is appropriate - particularly since the RM and AM aren't 'in sync' ever. Yes, this could lead to some waste, but the system is eventually consistent. > AM releases too many containers due to the protocol > --------------------------------------------------- > > Key: MAPREDUCE-2694 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-2694 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: mrv2 > Reporter: Arun C Murthy > Assignee: Arun C Murthy > > - AM sends request asking 4 containers on host H1. > - Asynchronously, host H1 reaches RM and gets assigned 4 containers. RM at this point, sets the value against H1 to > zero in its aggregate request-table for all apps. > - In the mean-while AM gets to need 3 more containers, so a total of 7 including the 4 from previous request. > - Today, AM sends the absolute number of 7 against H1 to RM as part of its request table. > - RM seems to be overriding its earlier value of zero against H1 to 7 against H1. And thus allocating 7 more > containers. > - AM already gets 4 in this scheduling iteration, but gets 7 more, a total of 11 instead of the required 7. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira