Mit Desai created YARN-3976:

             Summary: Catch ApplicationNotFoundException instead of parent 
YarnException in YarnClient and AppReportFetcher
                 Key: YARN-3976
             Project: Hadoop YARN
          Issue Type: Bug
    Affects Versions: 2.7.1
            Reporter: Mit Desai
            Assignee: Mit Desai

It's is better to catch the ApplicationNotFoundException rather than the parent 
YarnException and rethrow it when it's not ApplicationNotFoundExcepton
 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;

This message was sent by Atlassian JIRA

Reply via email to