You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2015/04/10 03:46:12 UTC

[jira] [Commented] (YARN-2421) CapacityScheduler still allocates containers to an app in the FINISHING state

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

Hadoop QA commented on YARN-2421:
---------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12663584/yarn2421.patch
  against trunk revision af9d4fe.

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new or modified test files.

      {color:red}-1 javac{color}.  The applied patch generated 1147 javac compiler warnings (more than the trunk's current 1146 warnings).

    {color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

    {color:green}+1 eclipse:eclipse{color}.  The patch built with eclipse:eclipse.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new Findbugs (version 2.0.3) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:red}-1 core tests{color}.  The patch failed these unit tests in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager:

                  org.apache.hadoop.yarn.server.resourcemanager.rmcontainer.TestRMContainerImpl

Test results: https://builds.apache.org/job/PreCommit-YARN-Build/7287//testReport/
Javac warnings: https://builds.apache.org/job/PreCommit-YARN-Build/7287//artifact/patchprocess/diffJavacWarnings.txt
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/7287//console

This message is automatically generated.

> 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, yarn2421.patch, 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.3.4#6332)