[
https://issues.apache.org/jira/browse/HADOOP-4053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634444#action_12634444
]
Steve Loughran commented on HADOOP-4053:
----------------------------------------
1. I'd expect jobCompleted() to be a no-op, and have jobRemoved() get called
when the job is removed.
2. There's a big assumption in JobTracker that the callbacks are fast and don't
block on anything, as the calls are synchronized on the JobTracker, the jobs
and the taskScheduler (always in that order). It may be wise to have a bundled
implementation that queues up the events and returns fast, so that people who
implement this interface (myself included) have a base implementation that
works the way the JobTracker expects; so things we add things like postings to
tuple-spaces or other notifications happen outside the synchronized block.
> Schedulers need to know when a job has completed
> ------------------------------------------------
>
> Key: HADOOP-4053
> URL: https://issues.apache.org/jira/browse/HADOOP-4053
> Project: Hadoop Core
> Issue Type: Improvement
> Affects Versions: 0.19.0
> Reporter: Vivek Ratan
> Assignee: Amar Kamat
> Fix For: 0.19.0
>
> Attachments: HADOOP-4053-v1.patch
>
>
> The JobInProgressListener interface is used by the framework to notify
> Schedulers of when jobs are added, removed, or updated. Right now, there is
> no way for the Scheduler to know that a job has completed. jobRemoved() is
> called when a job is retired, which can happen many hours after a job is
> actually completed. jobUpdated() is called when a job's priority is changed.
> We need to notify a listener when a job has completed (either successfully,
> or has failed or been killed).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
