[YARN-3976] Catch ApplicationNotFoundException instead of parent YarnException in YarnClient and AppReportFetcher

• Type: Bug
• Status: Resolved
• Priority: Trivial
• Resolution: Duplicate
• Affects Version/s: 2.7.1
• Target Version/s: 2.8.0
• Assignee: Mit Desai
• Reporter: Mit Desai
• Created: 24/Jul/15 20:49
• Updated: 23/Dec/15 19:38
• Resolved: 23/Sep/15 18:13

Description

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

Issue Links

• duplicates: YARN-3975 WebAppProxyServlet should not redirect to RM page if AHS is enabled