[
https://issues.apache.org/jira/browse/MAPREDUCE-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12725944#action_12725944
]
Hemanth Yamijala commented on MAPREDUCE-683:
--------------------------------------------
I looked at the patch. I think it is more natural to simply reset the
JobHistoryFileManager to a new instance in JobHistory.init(), instead of
defining a new API now. But this apparently leads to failures in unrelated test
cases - because JobHistory is enabled by default. My suggestion would be to
disable it for test cases and enable only in init.
> TestJobTrackerRestart fails with Map task completion events ordering mismatch
> -----------------------------------------------------------------------------
>
> Key: MAPREDUCE-683
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-683
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: jobtracker
> Reporter: Sreekanth Ramakrishnan
> Assignee: Amar Kamat
> Attachments: MAPREDUCE-683-v1.0.patch,
> TEST-org.apache.hadoop.mapred.TestJobTrackerRestart.txt
>
>
> {{TestJobTrackerRestart}} fails consistently with Map task completion events
> ordering mismatch error.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
