Manually Scaling Up Storage Space of a GeminiDB Influx Instance

Scenarios

This section describes how to scale up storage of an instance to suit your service requirements.

Usage Notes

Currently, storage can only be scaled up, not down, for cluster instances, single-node instances, and cluster (performance-enhanced) instances with cloud native storage.
You do not need to restart the instance while scaling its storage. The change has no impact on existing data, services, or your databases.

Billing

During the scale-up, you are billed for the original storage capacity. Once the scale-up is complete, billing switches to the new storage capacity.

**Table 1** Billing
Billing Mode	Operation	Impact on Price
Yearly/Monthly	Scaling up storage	You will be charged the price difference based on the remaining subscription period. Example (The specifications and prices below are for reference only. The actual prices are displayed on the console.) Assume that you purchased a yearly/monthly GeminiDB Influx instance with 40 GB of storage for one month on April 8, 2023, at a unit storage price of $1 USD/GB/month. On April 18, 2023, you added 40 GB of storage, bringing the total to 80 GB. The price difference is calculated as follows: Scale-up price = Added storage × Unit price × Remaining period The remaining period in the formula is calculated by dividing remaining days in each calendar month by the total days in that month. In this example, the remaining period is 0.6581 [12 (remaining days in April)/30 (total days in April) + 8 (remaining days in May)/31 (total days in May)]. The scale-up price is therefore $26.3 USD (40 × 1 × 0.6581). For details, see Yearly/Monthly Billing.
Pay-per-use	Scaling up storage	After storage is scaled up, a new order is generated and you will be billed at the new price. The old order is automatically invalidated. For details, see Pay-per-Use Billing.

Read-only Instance

To maintain instance stability, the system checks its storage every 10 seconds. If your GeminiDB Influx instance is running out of storage, it will become read-only and its data cannot be modified. If this happens, you can scale up the storage to restore the instance status.

Table 2 describes the read-only status of instances with classic storage.

**Table 2** Read-only status of instances with classic storage
Storage	Description
< 600 GB	When the storage usage reaches 97%, the instance becomes read-only. When the storage usage decreases to 85%, the instance exits the read-only mode.
≥ 600 GB	If the remaining storage is less than 18 GB, the instance becomes read-only. When the remaining storage is greater than or equal to 90 GB, the read-only status is automatically disabled.

Table 3 describes the read-only status of instances with cloud native storage.

**Table 3** Read-only status of instances with cloud native storage
Storage	Description
< 16,000 GB	When the storage usage reaches 97%, the instance becomes read-only. When the storage usage decreases to 85%, the instance exits the read-only mode.
≥ 16,000 GB	If the remaining storage is less than 480 GB, the instance becomes read-only. When the remaining storage is greater than or equal to 2,400 GB, the instance exits the read-only mode.

The kernel uses an LSM architecture. When written or deleted data reaches a certain amount, it will be merged. New data and old data to be deleted are stored together, and the disk usage increases temporarily based on the amount of merged data. In this case, the read-only status may be triggered. You are advised to reserve sufficient disk space to prevent the read-only status.

Procedure

Log in to the GeminiDB console.
Method 1:

On the Instances page, click the target instance name.

In the Storage Space area on the Basic Information page, click Scale.
Figure 1 Scaling up storage

Method 2:

On the Instances page, locate the target instance and choose More > Scale Storage Space in the Operation column.
Figure 2 Scaling up storage
On the displayed page, specify new storage and click Next.
- Instance with classic storage
  Figure 3 Scaling up storage
- Instance with cloud native storage
  Figure 4 Scaling up storage
  - Classic storage can be scaled up by at least 1 GB each time, and the value must be an integer.
  - Cloud native storage can be scaled up by at least 10 GB each time, and the value must be an integer multiple of 10.
On the displayed page, confirm the storage space.
- Yearly/Monthly
  - If you need to modify the settings, click Previous.
  - If you do not need to modify the settings, click Submit and complete the payment.
- Pay-per-use
  - If you need to modify the settings, click Previous.
  - If you do not need to modify the settings, click Submit.
Check the results.
- When the scale-up task is ongoing, the instance status is Scaling up.
- After the scale-up task is complete, the instance status becomes Available.
- Click the instance name. In the Storage Space area on the Basic Information page, you can view the new storage space.