Mailing-List: contact mapreduce-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-dev@hadoop.apache.org
Date: Fri, 15 Jul 2011 22:40:00 +0000 (UTC)
From: "Arun C Murthy (JIRA)" <jira@apache.org>
To: mapreduce-dev@hadoop.apache.org
Message-ID: 
 <1353413269.19066.1310769600008.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (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

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
            Reporter: Arun C Murthy
            Assignee: Sharad Agarwal


- 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