hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Chansler (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-5049) Jobs with 0 maps will never get removed from the default scheduler
Date Wed, 21 Jan 2009 23:59:59 GMT

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

Robert Chansler updated HADOOP-5049:
------------------------------------

    Fix Version/s: 0.20.0

> 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
>            Assignee: Amar Kamat
>            Priority: Blocker
>             Fix For: 0.20.0
>
>         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