[jira] Updated: (HADOOP-5049) Jobs with 0 maps will never get removed from the default scheduler

["Amar Kamat (JIRA)" <ji...@apache.org>]

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

Amar Kamat updated HADOOP-5049:
-------------------------------

    Attachment: HADOOP-5049-v1.1.patch

Attaching a patch that removes completed/failed job from default scheduler. 

> Jobs with 0 maps will never get removed from the default scheduler
> ------------------------------------------------------------------
>
>                 Key: HADOOP-5049
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5049
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>            Reporter: Amar Kamat
>            Priority: Blocker
>         Attachments: HADOOP-5049-v1.1.patch
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.