[jira] [Commented] (MAPREDUCE-6252) JobHistoryServer should not fail when encountering a missing directory

["Hadoop QA (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MAPREDUCE-6252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14512117#comment-14512117 ] 

Hadoop QA commented on MAPREDUCE-6252:
--------------------------------------

\\
\\
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | pre-patch |  14m 35s | Pre-patch trunk compilation is healthy. |
| {color:green}+1{color} | @author |   0m  0s | The patch does not contain any @author tags. |
| {color:green}+1{color} | tests included |   0m  0s | The patch appears to include 1 new or modified test files. |
| {color:green}+1{color} | whitespace |   0m  0s | The patch has no lines that end in whitespace. |
| {color:green}+1{color} | javac |   7m 31s | There were no new javac warning messages. |
| {color:green}+1{color} | javadoc |   9m 35s | There were no new javadoc warning messages. |
| {color:green}+1{color} | release audit |   0m 23s | The applied patch does not increase the total number of release audit warnings. |
| {color:green}+1{color} | checkstyle |   5m 23s | There were no new checkstyle issues. |
| {color:green}+1{color} | install |   1m 34s | mvn install still works. |
| {color:green}+1{color} | eclipse:eclipse |   0m 33s | The patch built with eclipse:eclipse. |
| {color:green}+1{color} | findbugs |   0m 42s | The patch does not introduce any new Findbugs (version 2.0.3) warnings. |
| {color:green}+1{color} | mapreduce tests |   5m 43s | Tests passed in hadoop-mapreduce-client-hs. |
| | |  46m  2s | |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL | http://issues.apache.org/jira/secure/attachment/12728095/MAPREDUCE-6252.1.patch |
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | trunk / dcc5455 |
| hadoop-mapreduce-client-hs test log | https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5450/artifact/patchprocess/testrun_hadoop-mapreduce-client-hs.txt |
| Test Results | https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5450/testReport/ |
| Console output | https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5450/console |


This message was 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, MAPREDUCE-6252.1.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)