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-6339) Job history file is not flushed correctly because isTimerActive flag is not set true when flushTimerTask is scheduled.
Date Wed, 29 Apr 2015 00:49:07 GMT

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

Hadoop QA commented on MAPREDUCE-6339:
--------------------------------------

\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | pre-patch |  14m 51s | Pre-patch trunk compilation is healthy. |
| {color:green}+1{color} | @author |   0m  0s | The patch does not contain any @author tags.
|
| {color:red}-1{color} | tests included |   0m  0s | 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{color} | whitespace |   0m  0s | The patch has no lines that end in whitespace.
|
| {color:green}+1{color} | javac |   7m 35s | There were no new javac warning messages. |
| {color:green}+1{color} | javadoc |   9m 38s | 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 |   5m 19s | The applied patch generated  1  additional
checkstyle issues. |
| {color:green}+1{color} | install |   1m 35s | mvn install still works. |
| {color:green}+1{color} | eclipse:eclipse |   0m 32s | The patch built with eclipse:eclipse.
|
| {color:green}+1{color} | findbugs |   0m 57s | The patch does not introduce any new Findbugs
(version 2.0.3) warnings. |
| {color:green}+1{color} | mapreduce tests |   8m 43s | Tests passed in hadoop-mapreduce-client-app.
|
| | |  49m 37s | |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL | http://issues.apache.org/jira/secure/attachment/12728944/MAPREDUCE-6339.001.patch
|
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | trunk / 5190923 |
| checkstyle | https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5469/artifact/patchprocess/checkstyle-result-diff.txt
|
| hadoop-mapreduce-client-app test log | https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5469/artifact/patchprocess/testrun_hadoop-mapreduce-client-app.txt
|
| Test Results | https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5469/testReport/
|
| Java | 1.7.0_55 |
| uname | Linux asf907.gq1.ygridcore.net 3.13.0-36-lowlatency #63-Ubuntu SMP PREEMPT Wed Sep
3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Console output | https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5469/console |


This message was automatically generated.

> Job history file is not flushed correctly because isTimerActive flag is not set true
when flushTimerTask is scheduled.
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-6339
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6339
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>    Affects Versions: 2.7.0
>            Reporter: zhihai xu
>            Assignee: zhihai xu
>            Priority: Critical
>         Attachments: MAPREDUCE-6339.000.patch, MAPREDUCE-6339.001.patch
>
>
> Job history file is not flushed correctly because isTimerActive flag is not set true
when flushTimerTask is scheduled.
> It looks like we should set isTimerActive to true when flushTimerTask is scheduled. Otherwise
if a new qualified event comes before the current flush timer is expired,  flushTimerTask
will be canceled and rescheduled.
> Also I didn't find any code which set isTimerActive flag to true, So isTimerActive is
useless in current code.



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

Mime
View raw message