hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karthik Kambatla (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1793) yarn application -kill doesn't kill UnmanagedAMs
Date Thu, 06 Mar 2014 20:10:44 GMT

    [ 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)

Mime
View raw message