You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Junping Du (JIRA)" <ji...@apache.org> on 2017/01/06 00:45:58 UTC
[jira] [Updated] (MAPREDUCE-6339) Job history file is not flushed
correctly because isTimerActive flag is not set true when flushTimerTask is
scheduled.
[ https://issues.apache.org/jira/browse/MAPREDUCE-6339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Junping Du updated MAPREDUCE-6339:
----------------------------------
Fix Version/s: 2.8.0
> 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.8.0, 2.7.1, 3.0.0-alpha1
>
> 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)
---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-help@hadoop.apache.org