Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Thu, 21 Aug 2014 20:43:11 +0000 (UTC)
From: "Chen He (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12734443.1408118670138.5608.1408653791627@arcas>
In-Reply-To: <JIRA.12734443.1408118670138@arcas>
References: <JIRA.12734443.1408118670138@arcas>
Subject: [jira] [Commented] (YARN-2421) CapacityScheduler still allocates
 containers to an app in the FINISHING state
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/YARN-2421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14105927#comment-14105927 ] 

Chen He commented on YARN-2421:
-------------------------------

[~lichangleo], is this "+    System.out.println("xxx inside test");" your debug code? If so, remove it from patch. :)

> CapacityScheduler still allocates containers to an app in the FINISHING state
> -----------------------------------------------------------------------------
>
>                 Key: YARN-2421
>                 URL: https://issues.apache.org/jira/browse/YARN-2421
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: scheduler
>    Affects Versions: 2.4.1
>            Reporter: Thomas Graves
>            Assignee: chang li
>         Attachments: yarn2421.patch
>
>
> I saw an instance of a bad application master where it unregistered with the RM but then continued to call into allocate.  The RMAppAttempt went to the FINISHING state, but the capacity scheduler kept allocating it containers.   We should probably have the capacity scheduler check that the application isn't in one of the terminal states before giving it containers. 


--
This message was sent by Atlassian JIRA
(v6.2#6252)