Batch Job Submission on NY Blue/L
As we had warned for some time, NY Blue/L now only offers dynamic partitions. No longer are predefined partitions also available. Class normal has been eliminated.
All jobs should be submitted to the compute nodes from the login node (i.e. from the front end node), as batch jobs via IBM's LoadLeveler. We are currently running LoadLeveler version 18.104.22.168 .
If your remaining node-hours for the month are not sufficient to run a job that you submit, the job filter will NOT permit your job to run, and it will display a message suggesting that you use one of the low priority classes.
But assuming you have sufficient node-hours to run your job, you can use one of the following normal priority classes. In your LoadLeveler batch script:
Class normaldyn jobs (48 hour wall clock limit) must specify the number of nodes on which to run the job, and the specified number must be 512 (512 nodes).
Class short jobs (24 hour wall clock limit) must specify the number of nodes on which to run the job, and the specified number must be either 1024, 2048, 3072, or 4096 (i.e. one, two, three, or four racks).
Class long jobs (72 hour wall clock limit) must specify the number of nodes on which to run the job, and the specified number must be either 32 or 128..
Notes for Classes Normaldyn, Short, and Long Jobs
Bear in mind that the batch system uses backfilling and favors incoming jobs with smaller specified wall clock limits, so it is to your advantage to specify a wall clock limit that is not larger than what your job will actually need.The Sample Loadleveler Batch Script hyperlink on the sidebar at left describes how to cancel a job, as well as usage of llq -s to learn about the status of a job.
There is a maximum wall clock limit of 48 hours on all class normaldyn LoadLeveler jobs, 24 hours on all class short jobs, and 72 hours on all class long jobs.
All jobs must specify the class to be used and the class must be normaldyn, short, or long, see the Sample LoadLeveler Batch Script hyperlink on the sidebar at the left which also discusses how to monitor LoadLeveler jobs and the meaning of the codes displayed when one monitors one's batch job.
maxjobs and maxqueued both equal 2 for class short and class shortlow, are 4 for class normaldyn and normaldynlow, and 6 for class long and longlow. The Notes section of the Sample LoadLeveler Batch Script hyperlink on the sidebar at the left explains the significance of this statement.
This site maintained by: firstname.lastname@example.org