[MAPREDUCE-683] TestJobTrackerRestart fails with Map task completion events ordering mismatch - ASF JIRA

XML

Word

Printable

JSON

Hadoop Flags:

Reviewed
Release Note:

Hide
TestJobTrackerRestart failed because of stale filemanager cache (which was created once per jvm). This patch makes sure that the filemanager is inited upon every JobHistory.init() and hence upon every restart. Note that this wont happen in production as upon a restart the new jobtracker will start in a new jvm and hence a new cache will be created.

Show
TestJobTrackerRestart failed because of stale filemanager cache (which was created once per jvm). This patch makes sure that the filemanager is inited upon every JobHistory.init() and hence upon every restart. Note that this wont happen in production as upon a restart the new jobtracker will start in a new jvm and hence a new cache will be created.
Tags:
ygridqa

TestJobTrackerRestart fails consistently with Map task completion events ordering mismatch error.

MAPREDUCE-683-v1.0.patch
30/Jun/09 19:37
0.8 kB
Amar Kamat
MAPREDUCE-683-v1.2.1-branch-0.20.patch
07/Jul/09 14:11
2 kB
Amar Kamat
MAPREDUCE-683-v1.2.patch
01/Jul/09 11:06
2 kB
Amar Kamat
MAPREDUCE-683-v1.2-branch-0.20.patch
07/Jul/09 13:43
2 kB
Amar Kamat
TEST-org.apache.hadoop.mapred.TestJobTrackerRestart.txt
30/Jun/09 10:30
255 kB
Sreekanth Ramakrishnan

is depended upon by

MAPREDUCE-237 Runtimes of TestJobTrackerRestart* testcases are high again