[
https://issues.apache.org/jira/browse/HADOOP-4053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634449#action_12634449
]
Hemanth Yamijala commented on HADOOP-4053:
------------------------------------------
bq. 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;
Are you suggesting having something like the following:
{code}
public class DefaultJobInProgressListener extends JobInProgressListener {
Queue<JobInProgress> completedJobs;
// ...
@override
public void jobCompleted(JobInProgress jip) [
completedJobs.add(jip);
}
// ...
}
{code}
And others would extend this class to take out events from the queues and act
on them, perhaps in a separate thread ?
> 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.
