Expand your storage pool size with drives managed by Portworx in AWS EKS

If you're running on the cloud, consider automation into your decision for which pool resize approach you use. The pxctl service pool expand command allows you to perform resize operations without manually adding new drives or increasing drive capacity on your cluster.

When you enter the pxctl service pool expand command, Portworx uses your cloud provider's API to create new drives and attach them or to expand the existing drives with no further input from you.

You can control the pool expand operation by specifying which operation you want to use: resize-drive or add-drive, or you can specify auto to let Portworx determine the best way to resize your storage pools based on your cloud provider.

By default, each pool can have a maximum of 6 drives. If required, you can use the runtime option limit_drives_per_pool to change this value.

The maximum number of drives for the AWS platform, including boot drives, Portworx cloud drives, and any other drives, is 8.

Limitations

• For an EBS volume converted from gp2 to gp3, Portworx does not update with the latest metadata such as IOPS, even after completing a pool maintenance cycle. As a result, you continue to see gp2 related details in the output of pxctl commands.
• Performing back-to-back pool expansions may cause AWS cloud drives to enter an Optimizing state. Once in this state, it may take up to 24 hours for AWS to permit further resizing. You can expand your pools again once drives are out of this state. This state can be monitored via the EBS volume UI or the aws cli. For more information, see the AWS documentation.

Automatically expand a cloud-based pool

1. Run the following command to find the UUID for a pool:

   pxctl service pool show

PX drive configuration:
Pool ID: 0
        UUID:  xxxxxxxx-xxxx-xxxx-xxxx-aef346e61d89
        IO Priority:  HIGH
        Labels:  iopriority=HIGH,medium=STORAGE_MEDIUM_SSD
        Size: 384 GiB
        Status: Online
        Has metadata:  Yes
        Balanced:  Yes
        Drives:
        1: /dev/sde, Total size 128 GiB, Online
        2: /dev/sdf, Total size 128 GiB, Online
        3: /dev/sdg, Total size 128 GiB, Online
        Cache Drives:
        No Cache drives found in this pool
Journal Device:
        1: /dev/sdc1, STORAGE_MEDIUM_SSD

2. Expand a cloud-based pool by entering the pxctl service pool expand command with the following options:

   • The --operation option to specify the desired operation
   • The --size option to set the minimum new size of the pool in GiB
   • The --uid option to provide the ID of the pool you want to resize

   pxctl service pool expand --operation auto --size 1000 --uid <pool-UUID>

   For example:

pxctl service pool expand --operation auto --size 1000 --uid xxxxxxxx-xxxx-xxxx-xxxx-aef346e61d89

3. Once you submit the command, Portworx will expand the storage pool in the background. You can list the storage pools periodically to check if they have finished expansion.

   pxctl cluster provision-status

4. When invoked on the Portworx node where the storage pool resides, the following command provides detailed information about the status of the pool expand process.

   pxctl service pool show

Resize or add a new drive to a cloud-based pool

note

You cannot add a new drive to the pool if your Portworx deployement is using PX-StoreV2 backend.

The auto operation automatically expands your pool capacity by increasing the pool size or adding the new drives to it. To perform a specific operation, replace auto with resize-drive or add-drive:

pxctl service pool expand --operation resize-drive --uid <pool-ID> --size <new-storage-pool-size-in-GiB>