Slurm configuration customization

Customize Slurm parameters for the entire cluster by using either the SlurmSettings / CustomSlurmSettings or the CustomSlurmSettingsIncludeFile parameter. AWS ParallelCluster fails if you specify both.

Customize Slurm parameters for a queue by using SlurmQueues / CustomSlurmSettings (mapped to Slurm partitions).

Customize Slurm parameters for a compute resource by using SlurmQueues / ComputeResources / CustomSlurmSettings (mapped to Slurm nodes).

For CustomSlurmSettings and CustomSlurmSettingsIncludeFile settings, you can only specify and update slurm.conf parameters that are included in the Slurm version that's supported by the AWS ParallelCluster version that you are using to configure a cluster.

If you specify custom Slurm configurations in any of the CustomSlurmSettings parameters, AWS ParallelCluster performs validation checks and prevents setting or updating Slurm configuration parameters that conflict with AWS ParallelCluster logic. The Slurm configuration parameters that are known to conflict with AWS ParallelCluster are identified in deny lists. The deny lists can change in future AWS ParallelCluster versions if other Slurm features are added. For more information, see Deny-listed Slurm configuration parameters for CustomSlurmSettings.

AWS ParallelCluster only checks whether a parameter is in a deny list. AWS ParallelCluster doesn't validate your custom Slurm configuration parameter syntax or semantics. You are responsible for validating your custom Slurm configuration parameters. Invalid custom Slurm configuration parameters can cause Slurm daemon failures that can lead to cluster create and update failures.

If you specify custom Slurm configurations in CustomSlurmSettingsIncludeFile, AWS ParallelCluster doesn't perform any validation.

You can update CustomSlurmSettings and CustomSlurmSettingsIncludeFile without stopping and starting the compute fleet. In this case, AWS ParallelCluster restarts the slurmctld daemon and runs the scontrol reconfigure command.

Some Slurm configuration parameters might require different operations before a change is registered in the entire cluster. For example, they might require a restart of all daemons in the cluster. You are responsible for verifying whether AWS ParallelCluster operations are sufficient for propagating your custom Slurm configuration parameter settings during updates. If you find that AWS ParallelCluster operations aren't sufficient, it's your responsibility to provide the additional actions required to propagate the updated settings as recommended in the Slurm documentation.