hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mit Desai (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (YARN-3976) Catch ApplicationNotFoundException instead of parent YarnException in YarnClient and AppReportFetcher
Date Wed, 23 Sep 2015 17:54:04 GMT

     [ https://issues.apache.org/jira/browse/YARN-3976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mit Desai resolved YARN-3976.
-----------------------------
       Resolution: Fixed
    Fix Version/s: 2.7.2

Made the change along with YARN-3975.
Resolving this jira as YARN-3975 is committed.

> Catch ApplicationNotFoundException instead of parent YarnException in YarnClient and
AppReportFetcher
> -----------------------------------------------------------------------------------------------------
>
>                 Key: YARN-3976
>                 URL: https://issues.apache.org/jira/browse/YARN-3976
>             Project: Hadoop YARN
>          Issue Type: Bug
>    Affects Versions: 2.7.1
>            Reporter: Mit Desai
>            Assignee: Mit Desai
>            Priority: Trivial
>             Fix For: 2.7.2
>
>
> It's is better to catch the ApplicationNotFoundException rather than the parent YarnException
and rethrow it when it's not ApplicationNotFoundExcepton
> {noformat}
>  catch (YarnException e) {
>       if (!historyServiceEnabled) {
>         // Just throw it as usual if historyService is not enabled.
>         throw e;
>       }
>       // Even if history-service is enabled, treat all exceptions still the same
>       // except the following
>       if (!(e.getClass() == ApplicationNotFoundException.class)) {
>         throw e;
>       }
> {noformat}



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

Mime
View raw message