ClusterPack Tutorial

% lsid

Find the queue definition you wish to modify. The following entries for maximum resource

usage can be modified or added for each queue definition:

CPULIMIT = minutes on a host

FILELIMIT = file size limit

MEMLIMIT = bytes per job

DATALIMIT = bytes for data segment

STACKLIMIT = bytes for stack

CORELIMIT = bytes for core files

PROCLIMIT = processes per job

RES_REQ is a resource requirement string specifying the condition for dispatching a job to a

host. Resource reservation and locality can also be specified in this string.

Groups of Compute Nodes created using clgroup are treated as resource requirements in

Clusterware Pro. If a group name is added as a RES_REQ to a queue, jobs submitted to that

queue will only run on nodes that are members of that group.

After adding, removing or modifying queues, it is necessary to reconfigure LSF to read the new

queue information. This is done from the Management Server using the Clusterware Pro V5.1

CLI:

% badmin reconfig

Verify the queue has been modified by using the Clusterware Pro V5.1 CLI:

% bqueues -l <queue_name>

References:

3.7.9 How do I access the Clusterware Pro V5.1 Command Line Interface?

1.8.5 Change priority of specified queues

The file /share/platform/clusterware/conf/lsbatch/<clustername>/configdir/lsb.queues controls

the priority of each queue.

The name of your cluster can be determined by using the Clusterware Pro V5.1 CLI:

lsid

Edit the lsb.queues file and look for a PRIORITY line for the queue you wish to change. If a

PRIORITY line exists, you can change the value specified. Otherwise, add a line of the form: