You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Jason Lowe (JIRA)" <ji...@apache.org> on 2015/09/23 20:13:05 UTC
[jira] [Reopened] (YARN-3976) Catch ApplicationNotFoundException
instead of parent YarnException in YarnClient and AppReportFetcher
[ https://issues.apache.org/jira/browse/YARN-3976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Lowe reopened YARN-3976:
------------------------------
> 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)