Return-Path: X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E227F1088C for ; Sun, 16 Jun 2013 02:59:25 +0000 (UTC) Received: (qmail 78287 invoked by uid 500); 16 Jun 2013 02:59:24 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 78237 invoked by uid 500); 16 Jun 2013 02:59:24 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-issues@hadoop.apache.org Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 78206 invoked by uid 99); 16 Jun 2013 02:59:22 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 16 Jun 2013 02:59:22 +0000 Date: Sun, 16 Jun 2013 02:59:22 +0000 (UTC) From: "Bikas Saha (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-779) AMRMClient should clean up dangling unsatisfied request MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13684548#comment-13684548 ] Bikas Saha commented on YARN-779: --------------------------------- That API is AMRMClient.removeContainerRequest(). > AMRMClient should clean up dangling unsatisfied request > ------------------------------------------------------- > > Key: YARN-779 > URL: https://issues.apache.org/jira/browse/YARN-779 > Project: Hadoop YARN > Issue Type: Bug > Components: client > Affects Versions: 2.0.4-alpha > Reporter: Alejandro Abdelnur > Assignee: Maysam Yabandeh > Priority: Critical > > If an AMRMClient allocates a ContainerRequest for 10 containers in node1 or node2 is placed (assuming a single rack) the resulting ResourceRequests will be > {code} > location - containers > --------------------- > node1 - 10 > node2 - 10 > rack - 10 > ANY - 10 > {code} > Assuming 5 containers are allocated in node1 and 5 containers are allocated in node2, the following ResourceRequests will be outstanding on the RM. > {code} > location - containers > --------------------- > node1 - 5 > node2 - 5 > {code} > If the AMMRClient does a new ContainerRequest allocation, this time for 5 containers in node3, the resulting outstanding ResourceRequests on the RM will be: > {code} > location - containers > --------------------- > node1 - 5 > node2 - 5 > node3 - 5 > rack - 5 > ANY - 5 > {code} > At this point, the scheduler may assign 5 containers to node1 and it will never assign the 5 containers node3 asked for. > AMRMClient should keep track of the outstanding allocations counts per ContainerRequest and when gets to zero it should update the the RACK/ANY decrementing the dangling requests. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira