LSF Version 7.3 - Platform LSF Configuration Reference

NICE
Syntax
NICE=integer
Description
Adjusts the UNIX scheduling priority at which jobs from this queue execute.
The default value of 0 (zero) maintains the default scheduling priority for UNIX interactive
jobs. This value adjusts the run-time priorities for batch jobs on a queue-by-queue basis, to
control their effect on other batch or interactive jobs. See the nice(1) manual page for more
details.
On Windows, this value is mapped to Windows process priority classes as follows:
•
nice>=0 corresponds to an priority class of IDLE
•
nice<0 corresponds to an priority class of NORMAL
Platform LSF on Windows does not support HIGH or REAL-TIME priority classes.
Default
0 (zero)
NQS_QUEUES
Syntax
NQS_QUEUES=NQS_ queue_name@NQS_host_name ...
Description
Makes the queue an NQS forward queue.
NQS_host_name is an NQS host name that can be the official host name or an alias name
known to the LSF master host.
NQS_queue_name is the name of an NQS destination queue on this host. NQS destination
queues are considered for job routing in the order in which they are listed here. If a queue
accepts the job, it is routed to that queue. If no queue accepts the job, it remains pending in
the NQS forward queue.
lsb.nqsmaps must be present for the LSF system to route jobs in this queue to NQS systems.
You must configure LSB_MAX_NQS_QUEUES in lsf.conf to specify the maximum
number of NQS queues allowed in the LSF cluster. This is required for LSF to work with NQS.
Since many features of LSF are not supported by NQS, the following queue configuration
parameters are ignored for NQS forward queues: PJOB_LIMIT, POLICIES, RUN_WINDOW,
DISPATCH_WINDOW, RUNLIMIT, HOSTS, MIG. The application-level RUNTIME
parameter in lsb.applications is also ignored. In addition, scheduling load threshold
parameters are ignored because NQS does not provide load information about hosts.
Default
Not defined
lsb.queues
Platform LSF Configuration Reference 305