Administering Platform LSF - SAS

Chapter 15
Goal-Oriented SLA-Driven Scheduling
The following illustrates the progress of the velocity SLA Comox running
100 jobs with random runtimes over a 14 hour period.
When an SLA is missing its goal
Use the CONTROL_ACTION parameter in your service class to configure an
action to be run if the SLA goal is delayed for a specified number of minutes.
CONTROL_ACTION (lsb.serviceclasses)
CONTROL_ACTION=VIOLATION_PERIOD[minutes] CMD [action]
If the SLA goal is delayed for longer than VIOLATION_PERIOD, the action
specified by CMD is invoked. The violation period is reset and the action runs
again if the SLA is still active when the violation period expires again. If the
SLA has multiple active goals that are in violation, the action is run for each of
them.
Example
CONTROL_ACTION=VIOLATION_PERIOD[10] CMD [echo `date`: SLA is
in violation >> ! /tmp/sla_violation.log]
Preemption and SLA policies
Chunk jobs and SLA policies
SLA jobs cannot be preempted. You should avoid running jobs belonging to
an SLA in low priority queues.
SLA jobs will not get chunked. You should avoid submitting SLA jobs to a
chunk job queue.
Administering Platform LSF 253