Return-Path: Delivered-To: apmail-lucene-hadoop-dev-archive@locus.apache.org Received: (qmail 11174 invoked from network); 28 Jun 2006 20:07:09 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 28 Jun 2006 20:07:09 -0000 Received: (qmail 94368 invoked by uid 500); 28 Jun 2006 20:07:08 -0000 Delivered-To: apmail-lucene-hadoop-dev-archive@lucene.apache.org Received: (qmail 94341 invoked by uid 500); 28 Jun 2006 20:07:08 -0000 Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hadoop-dev@lucene.apache.org Delivered-To: mailing list hadoop-dev@lucene.apache.org Received: (qmail 94332 invoked by uid 99); 28 Jun 2006 20:07:08 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Jun 2006 13:07:08 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [209.237.227.198] (HELO brutus.apache.org) (209.237.227.198) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Jun 2006 13:07:07 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id CD9E2410005 for ; Wed, 28 Jun 2006 20:05:31 +0000 (GMT) Message-ID: <12267443.1151525131839.JavaMail.jira@brutus> Date: Wed, 28 Jun 2006 20:05:31 +0000 (GMT+00:00) From: "Runping Qi (JIRA)" To: hadoop-dev@lucene.apache.org Subject: [jira] Updated: (HADOOP-322) Need a job control utility to submit and monitor a group of jobs which have DAG dependency In-Reply-To: <4931825.1151126129857.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/HADOOP-322?page=all ] Runping Qi updated HADOOP-322: ------------------------------ Attachment: (was: job_control_patch.txt) > 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 > > 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