Skip to main content
FlashGrid.io

Resizing database server (FlashGrid Server on AWS)

  • Updated
  • Products: FlashGrid Server on AWS

Resizing the AWS instance may be needed for performance or cost reasons. Resizing requires database downtime.

Preparation

Prior to resizing nodes, first confirm that your chosen instance type is supported by FlashGrid software. Choosing an unsupported instance type can result in the following error when trying to apply the change:

Failed to modify instance type for instance.
The instance configuration for this AWS Marketplace product is not supported. Please see the AWS Marketplace site for more information about supported instance types, regions, and operating systems.

Execute the following command to display a list of supported instance types:

$ flashgrid-clan-cfg show-supported-instance-types 
Detected EC2 instance type: c5.xlarge
Supported instance types:
c5.12xlarge
c5.18xlarge
c5.24xlarge
c5.2xlarge
[...]

You can use grep to find a particular instance type, i.e.

$ flashgrid-clan-cfg show-supported-instance-types | grep i3.metal
i3.metal

If your chosen instance type is not shown in the output, then it is not supported by the installed version of FlashGrid CLAN software. 

You can review Release Notes: FlashGrid Server (non-clustered) to determine if the instance type has been added in a newer release. To check which version you have installed, run:

$ rpm -q flashgrid-clan
flashgrid-clan-21.8.292.58899.3a5ad336.release-1.el8.x86_64

For access to download a newer version of FlashGrid software, or to request a review of your resizing options, raise a support case with FlashGrid.

Resize Node

  1. Update SGA and PGA sizing parameters for the databases according to the new AWS instance memory size. 

  2. Skip this step unless you have vm.nr_hugepages parameter in /etc/sysctl.conf manually configured. If you have it manually configured then update the parameters according to the new AWS instance size. Note that starting with Storage Fabric 19.02 HugePages are configured automatically by default and manual change is not required.

  3. Stop all running databases.

  4. Stop the FlashGrid server system. The following command will gracefully stop HAS, FlashGrid services and the AWS instance.

    # flashgrid-node poweroff

  5. Resize the AWS instance using AWS console. Custom CPU options can be set under Advanced details in the Change instance type view if needed.

  6. Start the AWS instance.

  7. Wait until all disk groups are mounted (Status = Good) by running flashgrid-dg.

  8. Start the databases stopped previously.

  9. On the server run flashgrid-health-check command to verify that the status is good and all checks have passed successfully.