[MAPREDUCE-27] Jobs with 0 maps will never get removed from the default scheduler

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Assignee: Amar Kamat
• Reporter: Amar Kamat
• Created: 15/Jan/09 08:56
• Updated: 20/Aug/09 11:37
• Resolved: 19/Aug/09 11:16

Description

Jobs' with 0 maps finish/succeed in the init phase i.e while the job is in the PREP state. EagerTaskInitializationListener removes the job after initing but JobQueueJobInProgressListener waits for a job-state change event to be raised and aonly then removes the job from the queue and hence the job will stay forever with the JobQueueJobInProgressListener. Looks like FairScheduler periodically scans the job list and removes completed jobs. CapacityScheduler has a concept of waiting jobs and scans waiting queue for completed jobs and purges them.

Issue Links

• is duplicated by: MAPREDUCE-805 Deadlock in Jobtracker