Mailing-List: contact yarn-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-dev@hadoop.apache.org
Date: Fri, 14 Mar 2014 17:28:45 +0000 (UTC)
From: "Zhijie Shen (JIRA)" <jira@apache.org>
To: yarn-dev@hadoop.apache.org
Message-ID: <JIRA.12701526.1394818108931.70842.1394818125136@arcas>
In-Reply-To: <JIRA.12701526.1394818108931@arcas>
References: <JIRA.12701526.1394818108931@arcas>
Subject: [jira] [Created] (YARN-1835) History client service needs to be
 more robust
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Zhijie Shen created YARN-1835:
---------------------------------

             Summary: History client service needs to be more robust
                 Key: YARN-1835
                 URL: https://issues.apache.org/jira/browse/YARN-1835
             Project: Hadoop YARN
          Issue Type: Bug
            Reporter: Zhijie Shen
            Assignee: Zhijie Shen


While doing the test, I've found the following issues so far:

1. The history file not found exception is exposed to the user directly, which is better to be caught and translated into ApplicationNotFound.
2. NPE will be exposed as well, since ApplicationHistoryManager doesn't do necessary null check.

In addition, TestApplicationHistoryManagerImpl missed to test most ApplicationHistoryManager methods.


--
This message was sent by Atlassian JIRA
(v6.2#6252)