Table of Contents

Revisions to Slurm Configuration v2.2.1 on Caviness

This document summarizes alterations to the Slurm job scheduler configuration on the Caviness cluster.

Issues

See this document discussing swap limits in Slurm jobs.

Implementation

The following aspects of the system construction will be observed in the configuration of the plugin:

These details produce the following configuration string:

partition(lg-swap)=none,host(r[00,01]n[00,56],r00g00)=1.1%/CPU,host(r[00,01]n[01-55]r[00-01]g[01-04],r1g00,r02s[00-01])=2.5%/CPU,host(r03n[00-57],r03g[00-08],r04n[00-76])=2.3%/CPU,default()=0MiB

Impact

No downtime is expected. The slurmd daemon must be restarted on all compute nodes, but currently-executing jobs/job steps should not be affected (they will reconnect to the new slurmd as necessary to communicate job status, etc.). The slurmctld daemons do not use the SPANK plugin, thus they do not need to be restarted.

Timeline

Date Time Goal/Description
2021-12-01 Authoring of this document
2021-12-0809:00Implementation