-sla
Specifies the service class where the job is to run.
Categories
properties
Synopsis
bsub -sla service_class_nameDescription
If the SLA does not exist or the user is not a member of the service class, the job is rejected.
If EGO-enabled SLA scheduling is configured with ENABLE_DEFAULT_EGO_SLA in lsb.params, jobs submitted without -sla are attached to the configured default SLA.
You can use -g with -sla. All jobs in a job group attached to a service class are scheduled as SLA jobs. It is not possible to have some jobs in a job group not part of the service class. Multiple job groups can be created under the same SLA. You can submit additional jobs to the job group without specifying the service class name again. You cannot use job groups with resource-based SLAs that have guarantee goals.
- If there is no service class attached to the /g1 job group, the specified sla1 service class is ignored.
- If there is a different SLA attached to the /g1 job group, the /g1 job group's service class replaces the specified sla1 service class.
LSF logs a warning message in the mbatchd log to notify you of these changes.
Use bsla to display the properties of service classes configured in LSB_CONFDIR/cluster_name/configdir/lsb.serviceclasses (see lsb.serviceclasses) and dynamic information about the state of each service class.
Examples
bsub -W 15 -sla Duncan sleep 100
Submit the UNIX command sleep together with its argument 100 as a job to the service class named Duncan.
The example submits and IBM PE job and assumes two hosts in cluster, hostA and hostB, each with 4 cores and 2 networks. Each network has one IB adapter with 64 windows.