Return-Path: 
 <yarn-issues-return-24086-apmail-hadoop-yarn-issues-archive=hadoop.apache.org@hadoop.apache.org>
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 4FE48104BB
	for <apmail-hadoop-yarn-issues-archive@minotaur.apache.org>;
 Thu,  6 Mar 2014 20:10:45 +0000 (UTC)
Received: (qmail 77268 invoked by uid 500); 6 Mar 2014 20:10:44 -0000
Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org
Received: (qmail 77245 invoked by uid 500); 6 Mar 2014 20:10:44 -0000
Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:yarn-issues-help@hadoop.apache.org>
List-Unsubscribe: <mailto:yarn-issues-unsubscribe@hadoop.apache.org>
List-Post: <mailto:yarn-issues@hadoop.apache.org>
List-Id: <yarn-issues.hadoop.apache.org>
Reply-To: yarn-issues@hadoop.apache.org
Delivered-To: mailing list yarn-issues@hadoop.apache.org
Received: (qmail 77237 invoked by uid 99); 6 Mar 2014 20:10:44 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Mar 2014 20:10:44 +0000
Date: Thu, 6 Mar 2014 20:10:44 +0000 (UTC)
From: "Karthik Kambatla (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12699253.1394136147740.17640.1394136644058@arcas>
In-Reply-To: <JIRA.12699253.1394136147740@arcas>
References: <JIRA.12699253.1394136147740@arcas>
Subject: [jira] [Commented] (YARN-1793) yarn application -kill doesn't kill
 UnmanagedAMs
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-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13922989#comment-13922989 ] 

Karthik Kambatla commented on YARN-1793:
----------------------------------------

{code}
    if (application.isAppSafeToTerminate()) {
      RMAuditLogger.logSuccess(callerUGI.getShortUserName(),
        AuditConstants.KILL_APP_REQUEST, "ClientRMService", applicationId);
      return KillApplicationResponse.newInstance(true);
    } else {
      this.rmContext.getDispatcher().getEventHandler()
        .handle(new RMAppEvent(applicationId, RMAppEventType.KILL));
      return KillApplicationResponse.newInstance(false);
    }
{code}
Looks like we don't do anything bug log and return if the app is unmanaged. If the AM continues to run, it continues to hold onto all the containers that were allocated to it. 

[~jianhe], [~vinodkv], [~bikassaha] - any thoughts off the top of your head? 

> yarn application -kill doesn't kill UnmanagedAMs
> ------------------------------------------------
>
>                 Key: YARN-1793
>                 URL: https://issues.apache.org/jira/browse/YARN-1793
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 2.3.0
>            Reporter: Karthik Kambatla
>            Assignee: Karthik Kambatla
>            Priority: Critical
>
> Trying to kill an Unmanaged AM though CLI (yarn application -kill <id>) logs a success, but doesn't actually kill the AM or reclaim the containers allocated to it.



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