[jira] Issue Comment Edited: (HADOOP-3740) Make JobInProgress pluggable

["Amar Kamat (JIRA)" <ji...@apache.org>]

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

amar_kamat edited comment on HADOOP-3740 at 7/10/08 5:10 AM:
-------------------------------------------------------------

This is what HADOOP-3412 is supposed to do, no? I am not sure of users need to control {{updateTaskInProgress}}. Alejandro, do you have any specific usecase?

      was (Author: amar_kamat):
    This is what the HADOOP-3412 is supposed to do, no? I am not sure of users need to control {{updateTaskInProgress}}. Alejandro, do you have any specific usecase?
  
> Make JobInProgress pluggable
> ----------------------------
>
>                 Key: HADOOP-3740
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3740
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: mapred
>         Environment: all
>            Reporter: Alejandro Abdelnur
>
> By allowing a pluggable JobInProgess it will be possible for provide implementations that can do a sophisticated task provisioning to the JobTracker. 
> For example, by providing alternate implementations of the {{obtainNewMapTask}}, {{obtainNewReduceTask}} and {{updateTaskInProgress}} it would be possible to implement a license server that allows to throttle use of external resources (ie webservices, databases) so at any given time there are not more than N tasks using a given resource. For this a task could be tagged with the names of external resources and the license server would keep track of the tasks running per tag, if the counter reaches zero then the {{obtainNew*Task}} method could return NULL instead of a task.
>  

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