LSF Version 7.3 - Platform LSF Configuration Reference

RTASK_GONE_ACTION
Syntax
RTASK_GONE_ACTION="[KILLJOB_TASKDONE | KILLJOB_TASKEXIT]
[IGNORE_TASKCRASH]"
Description
Defines the actions LSF should take if it detects that a remote task of a parallel or distributed
job is gone.
This parameter only applies to the blaunch distributed application framework.
IGNORE_TASKCRASH
A remote task crashes. LSF does nothing. The job continues to launch the next task.
KILLJOB_TASKDONE
A remote task exits with zero value. LSF terminates all tasks in the job.
KILLJOB_TASKEXIT
A remote task exits with non-zero value. LSF terminates all tasks in the job.
Environment variable
When defined in an application profile, the LSB_DJOB_RTASK_GONE_ACTION variable
is set when running bsub -app for the specified application.
You can also use the environment variable LSB_DJOB_RTASK_GONE_ACTION to override
the value set in the application profile.
Example
RTASK_GONE_ACTION="IGNORE_TASKCRASH KILLJOB_TASKEXIT"
Default
Not defined. LSF does nothing.
RUNLIMIT
Syntax
RUNLIMIT=[hour:]minute[/host_name | /host_model]
Description
The default run limit. The name of a host or host model specifies the runtime normalization
host to use.
By default, jobs that are in the RUN state for longer than the specified run limit are killed by
LSF. You can optionally provide your own termination job action to override this default.
Jobs submitted with a job-level run limit (bsub -W) that is less than the run limit are killed
when their job-level run limit is reached. Jobs submitted with a run limit greater than the
lsb.applications
Platform LSF Configuration Reference 181