hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (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 Thu, 30 Apr 2015 12:13:08 GMT

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

Hudson commented on MAPREDUCE-6339:
-----------------------------------

FAILURE: Integrated in Hadoop-Yarn-trunk-Java8 #179 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk-Java8/179/])
MAPREDUCE-6339. Job history file is not flushed correctly because (devaraj: rev f5b38477f9d0827b238fadd260c1dd2889531fd4)
* hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/jobhistory/JobHistoryEventHandler.java
* hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/test/java/org/apache/hadoop/mapreduce/jobhistory/TestJobHistoryEventHandler.java
* hadoop-mapreduce-project/CHANGES.txt


> 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
>             Fix For: 2.7.1
>
>         Attachments: MAPREDUCE-6339.000.patch, MAPREDUCE-6339.test.patch, MAPREDUCE-6339.test1.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