Overview of Scaling Up Storage Space
As more data is added, you may start to run out of space. This section describes how to scale up the storage space of a DB instance. See Table 1 for the methods of scaling up storage space of GaussDB.
|
Scale-up Method |
Supported Instance Type |
Scope |
Description |
|---|---|---|---|
|
All shards |
Shard-level scale-up is performed based on the selected storage space. All shards are scaled up at a time. The added storage space must be a multiple of 4 GB x Number of shards. |
|
|
Distributed |
|
Shard-level scale-up is performed based on the selected storage space. One or more shards are scaled up at a time. The added storage space must be a multiple of 4 GB. |
|
|
|
Shard-level scale-up is performed based on the user-defined scale-up step (specified by the Scale Up By parameter). When the available storage space of a DN component is less than or equal to the specified value, an automatic scale-up task is triggered to scale up the shard where the DN component with insufficient available storage space is located. Storage can be scaled by percentage or fixed size.
|
Manually Scaling Up Storage Space for an Instance
Take the distributed instances that are independently deployed as an example. If the instance is configured with 3 shards, 3 replicas, and 3 CNs by default, and the total storage space is 120 GB before scale-up, the storage space of each shard is 40 GB. If the added storage space is 12 GB, the total storage space will be 132 GB after scale-up. 4 GB is added to each shard, and the storage space of each shard is 44 GB.
Manually Scaling Up Storage Space of Specified Shards
Take the distributed instances that are independently deployed as an example. If the instance is configured with 3 shards, 3 replicas, and 3 CNs by default, and the total storage space is 120 GB before scale-up, the storage space of each shard is 40 GB. If 4 GB and 8 GB of storage spaces are added to shard 1 and shard 2 respectively, the total storage spaces of shard 1 and shard 2 are 44 GB and 48 GB respectively. The total storage space is 132 GB after scale-up.
Automatically Scaling Up Storage Space for an Instance
- By percentage
Take the distributed instances that are independently deployed as an example. If the instance is configured with 3 shards, 3 replicas, and 3 CNs by default, and the total storage space is 120 GB before scale-up, the storage space of each shard is 40 GB. In the scale-up policy, Trigger If Available Storage Drops To is set to 20%, and Scale Up By is set to 20%. If the available storage usage of shard 1 drops to 20% or lower, a scale-up action is automatically triggered. The added storage space of shard 1 is 8 GB (40 x 20%). After the scale-up, the storage space of shard 1 is 48 GB, and the total storage space of the instance is 128 GB.
Figure 3 Scaling up storage space
- By fixed size
Take the distributed instances that are independently deployed as an example. If the instance is configured with 3 shards, 3 replicas, and 3 CNs by default, and the total storage space is 120 GB before scale-up, the storage space of each shard is 40 GB. In the scale-up policy, Trigger If Available Storage Drops To is set to 20, and Scale Up By is set to 40 GB. If the available storage usage of the DN 1_1 and DN 3_3 components is less than or equal to 20%, a scale-up task is automatically triggered. The added storage space of shards where the DN 1_1 and DN 3_3 components are located is 40 GB. After scale-up, the total storage space is 200 GB. 40 GB is added to shard 1 and shard 3 respectively. The total storage spaces of shard 1 and shard 3 are both 80 GB.
Figure 4 Scaling up storage space
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot
