Details
-
Bug
-
Status: Closed
-
Critical
-
Resolution: Fixed
-
2.7.0
-
None
-
Reviewed
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.
Attachments
Attachments
Issue Links
- duplicates
-
MAPREDUCE-6348 JobHistoryEventHandler could not flush every 30 secondes
- Resolved