CreateFileSystemLustreMetadataConfiguration
The Lustre metadata performance configuration for the creation of an
Amazon FSx for Lustre file system using a PERSISTENT_2
deployment type. The configuration uses a Metadata IOPS value to set the
maximum rate of metadata disk IOPS supported by the file system.
After creation, the file system supports increasing metadata performance. For more information on Metadata IOPS, see Lustre metadata performance configuration in the Amazon FSx for Lustre User Guide.
Contents
- Mode
-
The metadata configuration mode for provisioning Metadata IOPS for an FSx for Lustre file system using a
PERSISTENT_2deployment type.-
In AUTOMATIC mode, FSx for Lustre provisions and scales Metadata IOPS for you. For SSD file systems, the number is based on storage capacity. For Intelligent-Tiering file systems, it is based on throughput capacity.
-
In USER_PROVISIONED mode, you specify the number of Metadata IOPS to provision for your file system.
Type: String
Valid Values:
AUTOMATIC | USER_PROVISIONEDRequired: Yes
-
- Iops
-
(USER_PROVISIONED mode only) Specifies the number of Metadata IOPS to provision for the file system. This parameter sets the maximum rate of metadata disk IOPS supported by the file system.
-
For SSD file systems, valid values are
1500,3000,6000,12000, and multiples of12000up to a maximum of192000. -
For Intelligent-Tiering file systems, valid values are
6000,12000, and multiples of12000up to a maximum of192000.
You can't provision fewer Metadata IOPS than AUTOMATIC mode provisions for your file system.
Note
Iopsdoesn’t have a default value. If you're using USER_PROVISIONED mode, you can choose to specify a valid value. If you're using AUTOMATIC mode, you cannot specify a value because FSx for Lustre automatically sets the value based on your file system's storage capacity for SSD file systems, and on throughput capacity for Intelligent-Tiering file systems.Type: Integer
Valid Range: Minimum value of 1500. Maximum value of 192000.
Required: No
-
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the following: