hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-107) ClientRMService.forceKillApplication() should handle the non-RUNNING applications properly
Date Thu, 25 Jul 2013 13:33:50 GMT

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

Jason Lowe commented on YARN-107:
---------------------------------

One thing to note here is some potential use-cases I can see for the CLI.  A user may be invoking
this in a script just to make sure the application is no longer running, and may not be thrilled
to see that it occasionally fails because the application happened to finish (successfully
or not) just before the kill request arrived.  In that case, will it be easy for their script
to differentiate between this race or an completely invalid app ID or some other fatal error?
 One way to solve that is to have the CLI support a flag stating it doesn't want the command
to report failure if the application is already in a terminal state when the kill command
arrives.
                
> ClientRMService.forceKillApplication() should handle the non-RUNNING applications properly
> ------------------------------------------------------------------------------------------
>
>                 Key: YARN-107
>                 URL: https://issues.apache.org/jira/browse/YARN-107
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 2.0.0-alpha
>            Reporter: Devaraj K
>            Assignee: Xuan Gong
>         Attachments: YARN-107.1.patch
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message