[ 
https://issues.apache.org/jira/browse/HADOOP-5532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12683859#action_12683859
 ] 

Amar Kamat commented on HADOOP-5532:
------------------------------------

I think we should add a new api in {{TaskScheduler}} named {{init()}}. 
{{init()}} will enable the scheduler to initialize its services and register 
them with the jobtracker. But start working/functioning only upon {{start()}}.  
Thoughts?

> Jobs should not be initialized while the recovery is in progress
> ----------------------------------------------------------------
>
>                 Key: HADOOP-5532
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5532
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: mapred
>            Reporter: Amar Kamat
>
> In the default case, the eager-task-initializer tries to init a job as soon 
> as its added. There is actually no need for external inits as recovery 
> manager itself does a forceful inits. The important thing is to enforce this 
> delay on inits across schedulers.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to