Manually Scaling Up Storage Space of Specified Shards

Scenarios

As more data is added, your GaussDB instance may start to run out of space. If the kernel system detects that the storage usage exceeds the predefined threshold, the instance is set to read-only and no data can be written to it. (The default threshold is 85%. You can modify the instance parameter cms:datastorage_threshold_value_check to change the usage threshold.) If the storage usage of the primary node exceeds the threshold while the standby node remains below it, the system triggers a primary/standby switchover. This process may cause intermittent service disconnections lasting several seconds or minutes. You can scale up the storage space of one or more specified shards. Services are not interrupted during storage scale-up.

Precautions

• This function is only available for distributed instances using independent deployment.
• Within the maximum allowed range, the storage usage cannot exceed the predefined threshold (85% by default) after the scale-up.
• If any node becomes faulty, submit a service ticket to contact the O&M engineers for troubleshooting before the scale-up.
• The storage space must be a multiple of (Number of shards x 4 GB).
• Each shard can hold up to 24 TB, so 24 TB of storage can be added for each shard added.
• If a DB instance is unavailable because the storage space is used up, you can scale up the storage space.
• You can scale up or down the storage of shards in an instance only when all existing shards have the same storage size.
• When you restore backup data to a new instance, the number of disks of the new instance is the number of disks in the largest shard of the original instance multiplied by the number of shards.

Constraints

• You can scale up storage space only when your account balance is greater than or equal to $0 USD.
• The maximum allowed storage is 24 TB. There is no limit on the number of scale-ups.
• The DB instance is in the Scaling up state when its storage is being scaled up. Backup services are not affected during this process.
• Reboot is not required during instance scale-up.
• You cannot reboot or delete an instance that is being scaled up.
• Storage space can only be scaled up, not down.

Billing

Procedure

1. Log in to the management console.
2. Click in the upper left corner and select a region and project.
3. Click in the upper left corner of the page and choose Databases > GaussDB.
4. On the Instances page, click the name of the target instance.
5. On the Basic Information page, click Scale Up Storage in the Shards field.
   Figure 1 Basic information
   

6. On the Scale Storage Space page, select target shards one by one, set the new storage space, and click Add to Scale. Then, click Next.
   Figure 2 Scaling up storage for specified shards
   

   Ensure that the usage of the new storage space is less than the predefined threshold (85% by default) after the scale-up. An instance can be restored from read-only to the read/write state only when the storage usage is lower than the specified threshold.

7. Confirm settings.
   • If you need to modify your settings, click Previous.
   • If your settings are correct, click Submit.

8. Check the result.

   During the scale-up, the instance status on the Instances page is shown as Scaling up. This process typically takes 3 to 5 minutes. After the scale-up is complete, click the instance name to go to the Basic Information page and check that the updated storage size is displayed.