hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Cutting (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-322) Need a job control utility to submit and monitor a group of jobs which have DAG dependency
Date Wed, 28 Jun 2006 20:45:33 GMT
    [ http://issues.apache.org/jira/browse/HADOOP-322?page=comments#action_12418312 ] 

Doug Cutting commented on HADOOP-322:
-------------------------------------

When I remove the 'try' block and add 'throws Exception' where required, the unit test still
passes, although all of the jobs fail:

% ant clean test -Dtestcase=TestJobControl

test:
    [mkdir] Created dir: /home/cutting/src/hadoop/build/test/data
    [mkdir] Created dir: /home/cutting/src/hadoop/build/test/logs
    [junit] Running org.apache.hadoop.jobs.TestJobControl
    [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 74.29 sec

BUILD SUCCESSFUL
Total time: 1 minute 22 seconds

Yet the log in build/test shows:

java.lang.OutOfMemoryError: Java heap space
Jobs are all done???
Jobs in waiting state: 0
Jobs in ready state: 0
Jobs in running state: 0
Jobs in success state: 0
Jobs in failed state: 4

Shouldn't the test fail if any of the jobs fail?


> 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
>         Type: New Feature

>     Reporter: Runping Qi
>     Assignee: Runping Qi
>  Attachments: job_control_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
submission.
> 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


Mime
View raw message