For all/general jobs requiring up to 48 cores, this is the queue.
Time limit of 96 hours(or 4 days) has been put on all all.q jobs.
Any job fired on this queue will get automatically terminated after 96 hours of running.
This is the queue for jobs that need a large number of cores and long time. In our context, large is 48 or more cores.
No time limit on largejob.q jobs.
This is the queue for testing out your MPI program to see if it works.
For the first time or after code modifications, or if you are running benchmarks to check run times.
Time limit for jobs: 6 hours. Any job in this queue running longer than 6 hours will get automatically terminated.
Total cores allocated for this queue: 128.
There are a total of 8 nodes (128 cores) allocated, so you should be able to do a full test, including IB.
Please keep your runs as short as possible, and the resources used to the minimum you need.
Running Job Policies
All jobs must be run through the batch schedulers on the cluster.
No jobs should be fired directly on the head node. It is reserved exclusively for login and interaction with the schedulers.
To login to any of the cluster facility, you will need to use SSH. See the FAQ entry for remote access for details.
All accounts on cluster machines are to be 'owned' by the research
advisor or head of the group. If for some reason you require individual
accounts for group membes, please contact Sumit Mookerjee.
Storage and Disk Space Usage
Users are not allowed to store data in home directory above some
specific limit which may vary depending upon requirement and
If you need more than 3 GB of space, please use the /mnt/oss partition on K2, or /mnt/pvfs2 on Kalki.
Users are not allowed to gain access to compute nodes directly via ssh and work from there.
All jobs that are to be run on the cluster must be submitted via the job schedulers. Please see the FAQ and the queue policies.
You may not run your programs in the background, or run ANY programs on the head node.
Jobs not conforming to these rules will be terminated and the user account may be locked.