[
https://issues.apache.org/jira/browse/MAPREDUCE-6339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhihai xu updated MAPREDUCE-6339:
---------------------------------
Description:
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.
was:
Job history file is not flushed correctly because isTimerActive flag is not set
true when flushTimerTask is scheduled. This looks like an apparent bug.
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.
> 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
> Attachments: MAPREDUCE-6339.000.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)
