Administering Platform LSF - SAS

Modifying a Built-In Load Index
Considerations
Steps
Chapter 9
Adding Resources
The ELIM can return values for the built-in load indices. In this case the value
produced by the ELIM overrides the value produced by the LIM.
◆
◆
◆
The ELIM must ensure that the semantics of any index it supplies are the
same as that of the corresponding index returned by the lsinfo(1)
command.
The name of an external load index must not be one of the resource name
aliases: cpu, idle, login, or swap. To override one of these indices, use
its formal name: r1m, it, ls, or swp as the ELIM output.
You must configure an external load index in lsf.shared even if you are
overriding a built-in load index.
For example, some sites prefer to use /usr/tmp for temporary files.
To override the tmp load index:
1 Write a program that periodically measures the space in the /usr/tmp file
system and writes the value to standard output. For details on format, see
“Writing an ELIM” on page 160.
For example, the program writes to its standard output:
1 tmp 47.5
2 Name the program elim and store it in the LSF_SERVERDIR directory.
All default load indices are local resources, so the elim must run locally
on every machine.
3 Define the resource.
Since the name of built-in load indices is not allowed in lsf.shared,
define a custom resource to trigger the elim.
For example:
Begin Resource
RESOURCENAME TYPE INTERVAL INCREASING DESCRIPTION
my_tmp Numeric 30 N (custom resource to trigger elim to
start up)
End Resource
4 Map the resource to hosts in lsf.cluster.cluster_name.
❖ To override the tmp load index on every host, specify the keyword
default:
Begin ResourceMap
RESOURCENAME
LOCATION
my_tmp
[default]
End ResourceMap
Administering Platform LSF 163