Partitions are used in Sandhills to enforce ownership and priority for owned resources. You can view the partitions with the command
|Shared||85||Shared resources||(default, no specification)|
|Software Engineering||8||Owned by Software Engineering|
|sabirianov||sabirianov||4||Owned by Renat Sabirianov||#SBATCH --partition=sabirianov|
|starace||starace||1||Owned by Anthony Starace||#SBATCH --partition=starace|
Specific CPU Frequency Selection
Sandhills is a hetereogenous cluster in terms of individual node resources, even when 'owned' by a research group and allocated to a specific partition with limited access. So that researchers can constrain their jobs' deployment to nodes with specific CPU frequencies, HCC has added a 'feature' on each node that can be used to filter as part of submission requests. Currently there are nodes with processors operating at 2300Mhz and 2000Mhz. In order to select only nodes of a specific frequency one must add '–contraint=2000Mhz' to the SLURM specification (for example). One can see partitions, node names, features, and allocation status by using a command such as 'sinfo -N -o "%P %f %t %N".
Limitations of Jobs
There are no special QoS settings for Sandhills currently. All jobs are subject to the maximum 10 day run time and 1000 jobs per user.
guest partition can be used by users and groups that do not own resources on Sandhills but still want to run parallel applications. Jobs running in the
guest partition will run on the owned resources with a high performance interconnect optimized for parallel applications. The jobs are preempted when the resources are needed by the resource owners and are restarted on another node.
Partitions marked as owned by a group means only specific groups are allowed to submit jobs to that partition. Groups are manually added to the list allowed to submit jobs to the partition. If you are unable to submit jobs to a partition, and you feel that you should be, please contact firstname.lastname@example.org.