Manually Scaling Up Storage Space of Specified Shards

Scenarios

As more data is added, you may start to run out of space. If the kernel system detects that the disk usage exceeds 85%, the instance is set to read-only and no data can be written to the DB instance. (85% is the default threshold. You can set the cms:datastorage_threshold_value_check parameter for an instance to change the usage threshold.) You can scale up the storage space of one or more specified shards. Services are not interrupted during storage scale-up.

Precautions

• Within the maximum allowed range, disk usage cannot exceed 85% of the total storage space after scaling.
• If any node becomes faulty, 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.
• The disk size of all shards must be the same.
• 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 space is being scaled up and the backup services are not affected.
• 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.

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 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 85%. An instance can be restored from read-only to the read/write state only when the disk usage is lower than 85%.

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

8. View the results.

   During the scale-up, the status of the instance on the Instances page is Scaling up. Later, click the instance name to go the Basic Information page and view the new storage space. This process may take 3 to 5 minutes.