hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Runping Qi (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-322) Need a job control utility to submit and monitor a group of jobs which have DAG dependency
Date Tue, 15 Aug 2006 21:39:14 GMT
     [ http://issues.apache.org/jira/browse/HADOOP-322?page=all ]

Runping Qi updated HADOOP-322:

               Status: Patch Available  (was: Open)
        Fix Version/s: 0.6.0
    Affects Version/s: 0.5.0

the sleep in the unit test is changed to 5 seconds from 60 seconds.
Also, UTF8 is replaced with Text.

The code is now in package org.apache.hadoop.mapred.jobcontrol.

> Need a job control utility to submit and monitor a group of jobs which have DAG dependency
> ------------------------------------------------------------------------------------------
>                 Key: HADOOP-322
>                 URL: http://issues.apache.org/jira/browse/HADOOP-322
>             Project: Hadoop
>          Issue Type: New Feature
>    Affects Versions: 0.5.0
>            Reporter: Runping Qi
>         Assigned To: Runping Qi
>             Fix For: 0.6.0
>         Attachments: jobcontrol_patch.txt
> In my applications, some jobs depend on the outputs of other jobs. Therefore, job dependency
forms a DAG. A job is ready to run if and only if it does not have any dependency or all the
jobs it depends are finished successfully. To help schedule and monitor a group of jobs like
that, I am thinking of implementing a utility that:
> 	- accept jobs with dependency specification
>       - monitor job status
>       - submit jobs when they are ready
> With such a utility, the application can construct its jobs, specify their dependency
and then hand the jobs to the utility class. The utility takes care of the details of job
> I'll post my design skech for comments/suggestion.
> Eventually, I'll submit a patch for the utility.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message