LSF: Difference between revisions

From Leo's Notes
This page was last edited on 21 January 2020, at 17:16.
Newer edit →
VisualWikitext
Created page with "Platform Load Sharing Facility (or simply LSF) is a job scheduler and workload manager developed by IBM. It is similar to Slurm. == Usage == === Tasks === {| class="wikit..."
 
mNo edit summary
Line 87: Line 87:


A job's run time limit can be adjusted using {{code|bmod -W HH:MM Job_ID}} or removed using {{code|bmod -Wn Job_ID}} .
A job's run time limit can be adjusted using {{code|bmod -W HH:MM Job_ID}} or removed using {{code|bmod -Wn Job_ID}} .
== See Also ==
* [https://www.ibm.com/support/knowledgecenter/en/SSETD4_9.1.2/lsf_command_ref/bjobs.1.html IBM Documentation: bjobs reference]
* [https://www.ibm.com/support/knowledgecenter/en/SSETD4_9.1.2/lsf_command_ref/lsadmin.8.html IBM Documentation: lsadmin reference]
* https://bmi.cchmc.org/resources/software/lsf-examples

Revision as of 17:16, 21 January 2020

Platform Load Sharing Facility (or simply LSF) is a job scheduler and workload manager developed by IBM. It is similar to Slurm.

Usage

Tasks

Command Description
bjobs -u all -a Shows all jobs of all users
bjobs 101 102 Shows jobs with job_ID 101 and 102
bsub Submits a batch job
bhosts Shows all host status
badmin LSF administration shell

Admin

Use the lsadmin and badmin commands to do most admin related things.

Startup

Use lsfstartup.

A Load Information Manager (LIM) daemon needs to be running on each server host. This daemon collects host load and configuration information and forwards it to the master LIM service on the master host.

A Remote Execution Server (RES) daemon needs to be running on each server host in order for them to accept remote execution requests.

To start LIM and RES on all hosts, run: 

# lsadmin limstartup all
# lsadmin resstartup all

sbatchd needs to be running on all hosts as well and can be started by running 

# badmin hstartup all

Restart

Use lsfrestart.

If some hosts are in a 'closed' state, you may need to restart LIM and RES on the host.

Fix 'closed' status by running on crick: 

## restart the 'lsf' service and also lim and res.
# lsadmin resrestart all
# lsadmin limrestart all

Shutdown

Use lsfshutdown to prevent users from submitting jobs.

To fully shut down, you must turn off sbatchd, LIM, and RES. 

# badmin  hshutdown all
# lsadmin resshutdown all
# lsadmin limshutdown all


Tasks

Extend Job Run Time

If a job was created with too little wall time (eg. bsub -W), you will see the following output when listing jobs using bjobs -WL, -WF, or -WP: 

# bjobs -u all -WL
JOBID   USER    STAT  QUEUE      FROM_HOST   EXEC_HOST   JOB_NAME   SUBMIT_TIME   TIME_LEFT
916742  user001 RUN   interactiv compute001  node001     bash       Jan  5 22:58     -       
933794  user001 RUN   normal     compute001  63*node001  *_de_novo. Jan 13 21:28  59:47 X    
934759  user001 RUN   normal     compute001  56*node001  *test_pasa Jan 17 16:21     -       
936079  user001 RUN   normal     compute001  56*node001  *e_guided. Jan 21 07:03  237:22 E

The TIME_LEFT column shows the time left in hours and minutes. The state is one of:

  • E: The job has an estimated run time that has not been exceeded.
  • L: The job has a hard run time limit specified but either has no estimated run time or the estimated run time is more than the hard run time limit.
  • X: The job has exceeded its estimated run time and the time displayed is the time remaining until the job reaches its hard run time limit.
  • -: A dash indicates that the job has no estimated run time and no run limit, or that it has exceeded its run time but does not have a hard limit and therefore runs until completion.

A job's run time limit can be adjusted using bmod -W HH:MM Job_ID or removed using bmod -Wn Job_ID .

See Also