[
https://issues.apache.org/jira/browse/MAPREDUCE-734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun C Murthy updated MAPREDUCE-734:
------------------------------------
Attachment: MAPREDUCE-734_0_20090708.patch
I had to fix this embarrassing bug my making a copy of the set of TaskTracker
objects in JobInProgress.cancelReserveSlots before calling
TaskTracker.unreserveSlots which calls JobInProgress.unreserveTaskTracker to
remove the TaskTracker object from the map. Oops! *hides*
> java.util.ConcurrentModificationException observed in unreserving slots for
> HiRam Jobs
> --------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-734
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-734
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: contrib/capacity-sched
> Reporter: Karam Singh
> Assignee: Arun C Murthy
> Attachments: MAPREDUCE-734_0_20090708.patch
>
>
> Ran jobs out which 3 were HiRAM, the job were not removed from scheduler
> queue even after they successfully completed
> hadoop queue -info queue -showJobs displays somwthing like -:
> job_200907080724_0031 2 1247059146868 username NORMAL 0 running
> map tasks using 0 map slots. 0 additional slots reserved. 0 running reduce
> tasks using 0 reduce slots. 60 additional slots reserved.
> job_200907080724_0030 2 1247059146972 username NORMAL 0 running
> map tasks using 0 map slots. 0 additional slots reserved. 0 running reduce
> tasks using 0 reduce slots. 60 additional slots reserved.
> But it does not block anything, but seems like zombie process of system
> Jobtracker log show java.util.ConcurrentModificationException
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.