Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
doku:job_chains [2014/06/03 13:18] irdoku:job_chains [2021/05/13 17:45] (current) – removed goldenberg
Line 1: Line 1:
-====== Job chains ====== 
- 
-Job chains are sets of consecutive **interdependent** jobs. 
- 
-There are several ways how to create job chains and we will discuss three different solutions below: 
-==== Solution I ===== 
-Create one single job script and list several different jobs inside it. E.g.: 
-<code> 
-user@l01 $ cat allInOne.sge 
-#$ -N allInOne 
- 
-./doJob1 
-./doJob2 
-./doJob3 
-</code> 
- 
-<code> 
-user@l01 $ qsub allInOne.sge 
-Your job 10411 ("allInOne") has been submitted. 
-</code> 
- 
- 
-==== Solution II ==== 
-In order to realize interdependencies of submitted jobs, qsub allows for the following options 
-*[-hold_jid job_identifier_list]          define jobnet interdependencies 
-*[-hold_jid_ad job_identifier_list]       define jobnet array interdependencies 
- 
--hold_jid <job id|job name>. 
- 
-<code> 
-user@l01 $ cat holdJob.sge 
-#$ -N holdJob 
- 
-./doJob1 
-</code> 
-<code> 
-user@l01 $ cat Job2.sge 
-#$ -N Job2 
-#$ -hold_jid holdJob 
- 
-./doJob2 
-</code> 
-... 
-<code> 
-user@l01 $ qsub holdJob.sge 
-Your job 10451 ("holdJob") has been submitted. 
-user@l01 $ qsub Job2.sge 
-Your job 10452 ("Job2") has been submitted. 
-user@l01 $ qsub Job3.sge 
-Your job 10453 ("Job3") has been submitted. 
-</code> 
-'Job2' waits and starts only after 'holdJob' has finished. If you have another 'Job3' it waits until 'Job2' has finished and so on ... . 
-   *Advantage: accumulates ”waiting time” 
-   *Note: -hold_jid <job_name> can only be used to reference jobs of the same user (-hold_jid <job_id> can be used to reference any job) 
  
  • doku/job_chains.1401801515.txt.gz
  • Last modified: 2014/06/03 13:18
  • by ir