You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2008/09/02 06:28:44 UTC
[jira] Commented: (HADOOP-3740) Make JobInProgress pluggable
[ https://issues.apache.org/jira/browse/HADOOP-3740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627574#action_12627574 ]
Hadoop QA commented on HADOOP-3740:
-----------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12389294/patch3740.txt
against trunk revision 691091.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 6 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs warnings.
+1 release audit. The applied patch does not increase the total number of release audit warnings.
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3154/testReport/
Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3154/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3154/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3154/console
This message is automatically generated.
> 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
> Attachments: patch3740.txt
>
>
> 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.