PREEMPT_DELAY=seconds
Preemptive jobs will wait the specified number of seconds from the submission time before preempting any low priority preemptable jobs. During the grace period, preemption will not be trigged, but the job can be scheduled and dispatched by other scheduling policies.
This feature can provide flexibility to tune the system to reduce the number of preemptions. It is useful to get better performance and job throughput. When the low priority jobs are short, if high priority jobs can wait a while for the low priority jobs to finish, preemption can be avoided and cluster performance is improved. If the job is still pending after the grace period has expired, the preemption will be triggered.
The waiting time is for preemptive jobs in the pending status only. It will not impact the preemptive jobs that are suspended.
The time is counted from the submission time of the jobs. The submission time means the time mbatchd accepts a job, which includes newly submitted jobs, restarted jobs (by brestart) or forwarded jobs from a remote cluster.
When the preemptive job is waiting, the pending reason is:
The preemptive job is allowing a grace period before preemption.
If you use an older version of bjobs, the pending reason is:
Unknown pending reason code <6701>;
The parameter is defined in lsb.params, lsb.queues (overrides lsb.params), and lsb.applications (overrides both lsb.params and lsb.queues).
Run badmin reconfig to make your changes take effect.
Not defined (if the parameter is not defined anywhere, preemption is immediate).