Thread: Job dependency and job_name

Hi,

I'm running Lava 1.0, and I'm testing its job dependency capability.

Specifically, I want job B to depend on job A being done:

bsub -w A -J B /path/to/executable

Job B will run after job A finishes if instead of 'A' I type in the job_ID of job A. But when I try to use its job_name (as in the example), job B stays pending, and tells me "Dependency condition invalid or never satisfied;".

What should I do? Simply using job_ID instead of the job_name is not a useful solution, unfortunately.

Thanks!

Originally Posted by jabburne

Hi,

I'm running Lava 1.0, and I'm testing its job dependency capability.

Specifically, I want job B to depend on job A being done:

bsub -w A -J B /path/to/executable

Job B will run after job A finishes if instead of 'A' I type in the job_ID of job A. But when I try to use its job_name (as in the example), job B stays pending, and tells me "Dependency condition invalid or never satisfied;".

What should I do? Simply using job_ID instead of the job_name is not a useful solution, unfortunately.

Thanks!

To avoid ambiguity issues, you can use unique job names ( generated with a name and timestamp for example ) when using job dependencies. The unique job names are generated as part of the job submission process.

If this is not possible, set the lsb.params parameter:
LSB_JOB_DEP_LAST_SUB = 1
This will tell the scheduler to consider only the last job with job names when
evaluating dependency conditions.

Hope this helps...

-shadowzone