[
https://issues.apache.org/jira/browse/HADOOP-5049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12666371#action_12666371
]
Owen O'Malley commented on HADOOP-5049:
---------------------------------------
I agree with Vivek. I think that changing the state of the job should always
generate the jobUpdated method.
That said, I think that we should not short-circuit maps with 0 jobs.
Especially, now that we have job initialization and clean up, it isn't the case
that jobs with maps = 0 will have no impact.
> 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.
