Skip to main content
FlashGrid.io

Resizing cluster nodes (FlashGrid Cluster on AWS)

  • Updated
  • Products: FlashGrid Cluster on AWS

Resizing cluster node VMs may be needed for performance or cost reasons. Resizing can be done for one node at a time without causing database downtime.

ATTENTION! The procedure below is mandatory for resizing from a newer instance type (r5b, r6i, m6i, c6i) to an older instance type (r5, m5, c5). An attempt to resize instances while the cluster is stopped (disk groups not mounted) will result in failure to mount the disk groups after the resize. More details available here.

To resize database nodes in a running cluster repeat the following steps on each database node, one node at a time

  1. Update SGA and PGA sizing parameters for the databases according to the new VM 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 VM size. Note that starting with Storage Fabric 19.02 HugePages are configured automatically by default and manual change is not required.

  3. Make sure there are no other nodes that are in offline or re-syncing state. All disk groups must have zero offline disks and Resync = No:

    # flashgrid-cluster

  4. Stop all local database instances running on the node.

  5. Stop Oracle CRS on the node:

    # crsctl stop crs

  6. Stop the FlashGrid Storage Fabric services on the node:

    # flashgrid-node stop

  7. Stop the VM using AWS console

  8. Resize the VM using AWS console

  9. Start the VM using AWS console

  10. Wait until all disks are back online and resyncing operations complete on all disk groups. All disk groups must have zero offline disks and Resync = No.

    # flashgrid-cluster

  11. Start all database instances on the node

  12. Proceed to the next node

To resize storage or quorum nodes in a running cluster repeat the following steps on each storage/quorum node, one node at a time

  1. Make sure there are no other nodes that are in offline or re-syncing state. All disk groups must have zero offline disks and Resync = No:

    # flashgrid-cluster

  2. Stop the FlashGrid Storage Fabric services on the node:

    # flashgrid-node stop

  3. Stop the VM using AWS console

  4. Resize the VM using AWS console

  5. Start the VM using AWS console

  6. Wait until all disks are back online and resyncing operations complete on all disk groups. All disk groups must have zero offline disks and Resync = No.

    # flashgrid-cluster
  7. Proceed to the next node

Keyword: EC2 instance upgrade