Skip to main content
FlashGrid.io

Resizing Database Server (FlashGrid Server on GCP)

  • Updated
  • Products: FlashGrid Server on GCP

Resizing the GCP 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. Execute the following command to display a list of supported instance types:

$ flashgrid-clan-cfg show-supported-instance-types
Detected GCP instance type: c3-standard-8
Supported instance types:
c3-highcpu-176
c3-highcpu-192-metal
c3-highcpu-22
c3-highcpu-4
c3-highcpu-44
[...]

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

$ flashgrid-clan-cfg show-supported-instance-types | grep c3-highmem-44
Detected GCP instance type: c3-standard-8
c3-highmem-44

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-24.11.20.80896.c7db978b.release-1.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 GCP 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 GCP 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 VM instance.

    # flashgrid-node poweroff
  5. Resize the VM using GCP console.
  6. Start the VM using GCP console.
  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.