hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xuan Gong (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-107) ClientRMService.forceKillApplication() should handle the non-RUNNING applications properly
Date Sun, 07 Jul 2013 03:31:50 GMT

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

Xuan Gong commented on YARN-107:
--------------------------------

Currently, if we try to kill an absent application by calling ClientRMService.forceKillApplication(),
it will simply throw out a YarnException. That works fine, but if the clients call yarn application
-kill ${unknow_ApplicationId} in commandline, they will get the exception. Sometimes, it will
let Clients confuse. The possible solution can be : We can create a exception, say NOTFOUNDException,
which extends from YarnException. Instead of just throwing out YarnException, we can add informations
in this exception and throw it out. And at Client or ApplicationCLI, we can catch this NOTFOUNDException,
and print out the message instead of print out the exception.
                
> 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
>


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