[
https://issues.apache.org/jira/browse/YARN-2421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14106384#comment-14106384
]
Advertising
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/12663498/yarn2421.patch
against trunk revision .
{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:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler 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:red}-1 release audit{color}. The applied patch generated 3
release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/4693//testReport/
Release audit warnings:
https://builds.apache.org/job/PreCommit-YARN-Build/4693//artifact/trunk/patchprocess/patchReleaseAuditProblems.txt
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/4693//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
>
>
> 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)
