[
https://issues.apache.org/jira/browse/MAPREDUCE-6252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14315378#comment-14315378
]
Hadoop QA commented on MAPREDUCE-6252:
--------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12697889/MAPREDUCE-6252.0.patch
against trunk revision d5855c0.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:red}-1 findbugs{color}. The patch appears to introduce 2 new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-common-project/hadoop-common
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5182//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5182//artifact/patchprocess/newPatchFindbugsWarningshadoop-common.html
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5182//console
This message is automatically generated.
> JobHistoryServer should not fail when encountering a missing directory
> ----------------------------------------------------------------------
>
> Key: MAPREDUCE-6252
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6252
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: jobhistoryserver
> Affects Versions: 2.6.0
> Reporter: Craig Welch
> Assignee: Craig Welch
> Attachments: MAPREDUCE-6252.0.patch
>
>
> The JobHistoryServer maintains a cache of job serial number parts to dfs
> paths which it uses when seeking a job it no longer has in its memory cache,
> multiple directories for a given serial number differentiated by time stamp.
> At present the jobhistory server will fail any time it attempts to find a job
> in a directory which no longer exists based on that cache - even though the
> job may well exist in a different directory for the serial number. Typically
> this is not an issue, but the history cleanup process removes the directory
> from dfs before removing it from the cache which leaves a window of time
> where a directory may be missing from dfs which is present in the cache,
> resulting in failure. For some dfs's it appears that the top level directory
> may become unavailable some time before the full deletion of the tree
> completes which extends what might otherwise be a brief period of failure to
> a more extended period. Further, this also places the service at the mercy
> of outside processes which might remove those directories. The proposal is
> simply to make the server resistant to this state such that encountering this
> missing directory is not fatal and the process will continue on to seek it
> elsewhere.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
