hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amar Kamat (JIRA)" <j...@apache.org>
Subject [jira] Updated: (MAPREDUCE-683) TestJobTrackerRestart fails with Map task completion events ordering mismatch
Date Tue, 07 Jul 2009 16:32:14 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Amar Kamat updated MAPREDUCE-683:
---------------------------------

    Release Note: 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.

> 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
>    Affects Versions: 0.21.0
>            Reporter: Sreekanth Ramakrishnan
>            Assignee: Amar Kamat
>             Fix For: 0.21.0
>
>         Attachments: MAPREDUCE-683-v1.0.patch, MAPREDUCE-683-v1.2-branch-0.20.patch,
MAPREDUCE-683-v1.2.1-branch-0.20.patch, MAPREDUCE-683-v1.2.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.


Mime
View raw message