[queue] section - AWS ParallelCluster

[queue] section

Defines configuration settings for a single queue. [queue] sections are only supported when scheduler is set to slurm.

The format is [queue <queue-name>]. queue-name must start with a lowercase letter, contain no more than 30 characters, and only contain lowercase letters, numbers, and hyphens (-).

[queue q1] compute_resource_settings = i1,i2 placement_group = DYNAMIC enable_efa = true disable_hyperthreading = false compute_type = spot
Note

Support for the [queue] section was added in AWS ParallelCluster version 2.9.0.

compute_resource_settings

(Required) Identifies the [compute_resource] sections containing the compute resources configurations for this queue. The section names must start with a letter, contain no more than 30 characters, and only contain letters, numbers, hyphens (-), and underscores (_).

Up to three (3) [compute_resource] sections are supported for each [queue] section.

For example, the following setting specifies that the sections that start [compute_resource cr1] and [compute_resource cr2] are used.

compute_resource_settings = cr1, cr2

Update policy: If this setting is changed, the update is not allowed.

compute_type

(Optional) Defines the type of instances to launch for this queue. This setting replaces the cluster_type setting.

Valid options are: ondemand, and spot.

The default value is ondemand.

For more information about Spot Instances, see Working with Spot Instances.

Note

Using Spot Instances requires that the AWSServiceRoleForEC2SpotFleet service-linked role exist in your account. To create this role in your account using the AWS CLI, run the following command:

aws iam create-service-linked-role --aws-service-name spotfleet.amazonaws.com

For more information, see Spot Fleet permissions in the Amazon EC2 User Guide for Linux Instances.

The following example uses SpotInstances for the compute nodes in this queue.

compute_type = spot

Update policy: The compute fleet must be stopped for this setting to be changed for an update.

disable_hyperthreading

(Optional) Disables hyperthreading on the nodes in this queue. Not all instance types can disable hyperthreading. For a list of instance types that support disabling hyperthreading, see CPU cores and threads for each CPU core per instance type in the Amazon EC2 User Guide for Linux Instances. If the disable_hyperthreading setting in the [cluster] section is defined, then this setting cannot be defined.

The default value is false.

disable_hyperthreading = true

Update policy: The compute fleet must be stopped for this setting to be changed for an update.

enable_efa

(Optional) If set to true, specifies that Elastic Fabric Adapter (EFA) is enabled for the nodes in this queue. EFA is supported by the following instance types (c5n.18xlarge, c5n.metal, g4dn.metal, i3en.24xlarge, i3en.metal, m5dn.24xlarge, m5n.24xlarge, m5zn.12xlarge, m5zn.metal, r5dn.24xlarge, r5n.24xlarge, p3dn.24xlarge, and p4d.24xlarge) on these operating systems (alinux, alinux2, centos7, centos8, ubuntu1604, or ubuntu1804). For more information, see Elastic Fabric Adapter. If the enable_efa setting in the [cluster] section is defined, then this setting cannot be defined.

enable_efa = true

Update policy: The compute fleet must be stopped for this setting to be changed for an update.

enable_efa_gdr

(Optional) If true, specifies that Elastic Fabric Adapter (EFA) GPUDirect RDMA (remote direct memory access) is enabled for the nodes in this queue. Setting this setting to true requires that the enable_efa_gdr setting is set to true .EFA GPUDirect RDMA is supported by the following instance types (p4d.24xlarge) on these operating systems (alinux, alinux2, centos7, centos8, ubuntu1604, or ubuntu1804). If the enable_efa_gdr setting in the [cluster] section is defined, then this setting cannot be defined.

The default value is false.

enable_efa_gdr = true

Update policy: The compute fleet must be stopped for this setting to be changed for an update.

placement_group

(Optional) If present, defines the placement group for this queue. This setting replaces the placement_group setting.

Valid options are the following values:

  • DYNAMIC

  • An existing Amazon EC2 cluster placement group name

When set to DYNAMIC, a unique placement group for this queue is created and deleted as part of the cluster stack.

For more information about placement groups, see Placement groups in the Amazon EC2 User Guide for Linux Instances. If the same placement group is used for different instance types, it’s more likely that the request might fail due to an insufficient capacity error. For more information, see Insufficient instance capacity in the Amazon EC2 User Guide for Linux Instances.

There is no default value.

Not all instance types support cluster placement groups. For example, t2.micro doesn't support cluster placement groups. For information about the list of instance types that support cluster placement groups, see Cluster placement group rules and limitations in the Amazon EC2 User Guide for Linux Instances. See Placement groups and instance launch issues for tips when working with placement groups.

placement_group = DYNAMIC

Update policy: The compute fleet must be stopped for this setting to be changed for an update.