LSF Version 7.3 - Administering Platform LSF

Understanding Service Class Behavior
354 Administering Platform LSF
SLA statistics files
Each active SLA goal generates a statistics file for monitoring and analyzing the
system. When the goal becomes inactive the file is no longer updated. The files are
created in the
LSB_SHAREDIR/cluster_name/logdir/SLA directory. Each file
name consists of the name of the service class and the goal type.
For example the file named
Quadra.deadline is created for the deadline goal of the
service class name
Quadra. The following file named Tofino.velocity refers to a
velocity goal of the service class named
Tofino:
cat Tofino.velocity
# service class Tofino velocity, NJOBS, NPEND (NRUN + NSSUSP + NUSUSP), (NDONE + NEXIT)
17/9 15:7:34 1063782454 2 0 0 0 0
17/9 15:8:34 1063782514 2 0 0 0 0
17/9 15:9:34 1063782574 2 0 0 0 0
# service class Tofino velocity, NJOBS, NPEND (NRUN + NSSUSP + NUSUSP), (NDONE + NEXIT)
17/9 15:10:10 1063782610 2 0 0 0 0
Job groups and SLA scheduling
Job groups provide a method for assigning arbitrary labels to groups of jobs.
Typically, job groups represent a project hierarchy. You can use
-g with -sla at job
submission to attach all jobs in a job group to a service class and have them
scheduled as SLA jobs and subject to the scheduling policy of the SLA. Within the
job group, resources are allocated to jobs on a fairshare basis.
All jobs submitted to a group under an SLA automatically belong to the SLA itself.
You cannot modify a job group of a job that is attached to an SLA.
A job group hierarchy can belong to only one SLA.
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.
If the specified job group does not exist, it is created and attached to the SLA.
You can also use
-sla to specify a service class when you create a job group with
bgadd.
View job groups attached to an SLA (bjgroup)
1 Run bjgroup to display job groups attached to a service class:
bjgroup
GROUP_NAME NJOBS PEND RUN SSUSP USUSP FINISH SLA JLIMIT OWNER
/fund1_grp 5 4 0 1 0 0 Venezia 1/5 user1
/fund2_grp 11 2 5 0 0 4 Venezia 5/5 user1
/bond_grp 2 2 0 0 0 0 Venezia 0/- user2
/risk_grp 2 1 1 0 0 0 () 1/- user2
/admi_grp 4 4 0 0 0 0 () 0/- user2
bjgroup
displays the name of the service class that the job group is attached to
with
bgadd -sla service_class_name. If the job group is not attached to any
service class, empty parentheses () are displayed in the SLA name column.