hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-6251) JobClient needs additional retries at a higher level to address not-immediately-consistent dfs corner cases
Date Sat, 25 Apr 2015 00:47:39 GMT

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

Hadoop QA commented on MAPREDUCE-6251:
--------------------------------------

\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | pre-patch |  14m 46s | 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 42s | There were no new javac warning messages. |
| {color:green}+1{color} | javadoc |  10m  1s | 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:red}-1{color} | checkstyle |   4m 30s | The applied patch generated  1  additional
checkstyle issues. |
| {color:green}+1{color} | install |   1m 49s | mvn install still works. |
| {color:green}+1{color} | eclipse:eclipse |   0m 37s | The patch built with eclipse:eclipse.
|
| {color:green}+1{color} | findbugs |   2m 14s | The patch does not introduce any new Findbugs
(version 2.0.3) warnings. |
| {color:green}+1{color} | mapreduce tests |   1m 49s | Tests passed in hadoop-mapreduce-client-core.
|
| {color:red}-1{color} | mapreduce tests | 102m 38s | Tests failed in hadoop-mapreduce-client-jobclient.
|
| | | 146m 31s | |
\\
\\
|| Reason || Tests ||
| Timed out tests | org.apache.hadoop.mapreduce.v2.TestMRJobs |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL | http://issues.apache.org/jira/secure/attachment/12728064/MAPREDUCE-6251.2.patch
|
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | trunk / 4a3dabd |
| checkstyle | https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5449/artifact/patchprocess/checkstyle-result-diff.txt
|
| hadoop-mapreduce-client-core test log | https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5449/artifact/patchprocess/testrun_hadoop-mapreduce-client-core.txt
|
| hadoop-mapreduce-client-jobclient test log | https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5449/artifact/patchprocess/testrun_hadoop-mapreduce-client-jobclient.txt
|
| Test Results | https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5449/testReport/
|
| Console output | https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5449/console |


This message was automatically generated.

> JobClient needs additional retries at a higher level to address not-immediately-consistent
dfs corner cases
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-6251
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6251
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: jobhistoryserver, mrv2
>    Affects Versions: 2.6.0
>            Reporter: Craig Welch
>            Assignee: Craig Welch
>         Attachments: MAPREDUCE-6251.0.patch, MAPREDUCE-6251.1.patch, MAPREDUCE-6251.2.patch
>
>
> The JobClient is used to get job status information for running and completed jobs. 
Final state and history for a job is communicated from the application master to the job history
server via a distributed file system - where the history is uploaded by the application master
to the dfs and then scanned/loaded by the jobhistory server.  While HDFS has strong consistency
guarantees not all Hadoop DFS's do.  When used in conjunction with a distributed file system
which does not have this guarantee there will be cases where the history server may not see
an uploaded file, resulting in the dreaded "no such job" and a null value for the RunningJob
in the client.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message