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] Commented: (MAPREDUCE-27) Jobs with 0 maps will never get removed from the default scheduler
Date Thu, 20 Aug 2009 11:29:14 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745398#action_12745398
] 

Amar Kamat commented on MAPREDUCE-27:
-------------------------------------

MAPREDUCE-805

> Jobs with 0 maps will never get removed from the default scheduler
> ------------------------------------------------------------------
>
>                 Key: MAPREDUCE-27
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-27
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>            Reporter: Amar Kamat
>            Assignee: Amar Kamat
>         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.


Mime
View raw message