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

Hadoop QA commented on YARN-2853:
---------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12681151/YARN-2853.2.patch
  against trunk revision 782abbb.

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

    {color:green}+1 tests included{color}.  The patch appears to include 2 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: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 test build failed 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/5829//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5829//console

This message is automatically generated.

> Killing app may hang while AM is unregistering
> ----------------------------------------------
>
>                 Key: YARN-2853
>                 URL: https://issues.apache.org/jira/browse/YARN-2853
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Jian He
>            Assignee: Jian He
>         Attachments: YARN-2853.1.patch, YARN-2853.1.patch, YARN-2853.2.patch
>
>
> When killing an app, app first moves to KILLING state, If RMAppAttempt 
> receives the attempt_unregister event before attempt_kill event,  it'll 
> ignore the later attempt_kill event.  Hence, RMApp won't be able to move to 
> KILLED state and stays at KILLING state forever.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to