LSF Version 7.3 - Platform LSF Configuration Reference

The following operating systems do not support the memory limit at the OS level and the job

is allowed to run without a memory limit:

•

Windows

•

Sun Solaris 2.x

Default

Not defined. Per-process memory limit enforced by the OS; per-job memory limit enforced

by LSF disabled

Notes

To make LSB_JOB_MEMLIMIT take effect, use the command badmin hrestart all to

restart all sbatchds in the cluster.

If LSB_JOB_MEMLIMIT is set, it overrides the setting of the parameter

LSB_MEMLIMIT_ENFORCE. The parameter LSB_MEMLIMIT_ENFORCE is ignored.

The difference between LSB_JOB_MEMLIMIT set to y and LSB_MEMLIMIT_ENFORCE set

to y is that with LSB_JOB_MEMLIMIT, only the per-job memory limit enforced by LSF is

enabled. The per-process memory limit enforced by the OS is disabled. With

LSB_MEMLIMIT_ENFORCE set to y, both the per-job memory limit enforced by LSF and

the per-process memory limit enforced by the OS are enabled.

Changing the default Terminate job control action: You can define a different Terminate

action in lsb.queues with the parameter JOB_CONTROLS if you do not want the job to be

killed. For more details on job controls, see Administering Platform LSF.

Limitations

If a job is running and the parameter is changed, LSF is not able to reset the type of limit

enforcement for running jobs.

•

If the parameter is changed from per-process limit enforced by the OS to per-job limit

enforced by LSF (LSB_JOB_MEMLIMIT=n or not defined changed to

LSB_JOB_MEMLIMIT=y), both per-process limit and per-job limit affect the running job.

This means that signals may be sent to the job either when the memory allocated to an

individual process exceeds the memory limit or the sum of memory allocated to all

processes of the job exceed the limit. A job that is running may be killed by LSF.

•

If the parameter is changed from per-job limit enforced by LSF to per-process limit

enforced by the OS (LSB_JOB_MEMLIMIT=y changed to LSB_JOB_MEMLIMIT=n or

not defined), the job is allowed to run without limits because the per-process limit was

previously disabled.