TencentDB for MySQL supports quick adjustment of instance specification and allows flexible scaling operations in the console. You can elastically adjust the specifications of MySQL instances according to your actual business conditions (at the initial stage, at the rapid development stage, during peak hours, or during off-peak hours), so as to better meet your needs such as full utilization of resources and real-time cost optimization. For details on instance adjustment fees, see Instance Adjustment Fee.
Note:You can view disk space on the instance details page in the MySQL console, or receive disk alarms according to the Alarm Policies (Cloud Monitor).
By default, the instance configuration is adjusted in the normal mode, which requires a data migration for the adjustment to complete after you adjust the instance configuration in the console. But if the physical machine where the instance is located has sufficient remaining resources (aka local resources), you can choose the QuickChange mode. The adjustment process is as follows:
Note:
- If the local resources are sufficient and meet the conditions of the QuickChange mode, this mode will be used by default. If you don't need to use it, you can disable it by toggling it off on the configuration adjustment page.
- In the QuickChange mode, the instance may be restarted and unavailable for a short time during configuration adjustment.
Isolation Policy | CPU and Memory | Maximum IOPS | Storage Space |
---|---|---|---|
General | 1-core 1000 MB | 1200 | 25–3000 GB |
1-core 2000 MB | 2000 | ||
2-core 4000 MB | 4000 | ||
4-core 8000 MB | 8000 | ||
4-core 16000 MB | 14000 | ||
8-core 16000 MB | 20000 | ||
8-core 32000 MB | 28000 | ||
16-core 32000 MB | 32000 | ||
16-core 64000 MB | 40000 | ||
16-core 96000 MB | 40000 | ||
16-core 128000 MB | 40000 | 25–6000GB | |
24-core 244000 MB | 60000 | ||
32-core 256000 MB | 80000 | ||
48-core 488000 MB | 120000 | ||
Dedicated | 2-core 16000 MB | 8000 | 25–3000 GB |
4-core 16000 MB | 10000 | ||
4-core 24000 MB | 13000 | ||
4-core 32000 MB | 16000 | ||
8-core 32000 MB | 32000 | ||
8-core 48000 MB | 36000 | ||
8-core 64000 MB | 40000 | ||
12-core 48000 MB | 36000 | 25–6000 GB | |
16-core 64000 MB | 60000 | ||
12-core 72000 MB | 40000 | ||
12-core 96000 MB | 48000 | ||
16-core 96000 MB | 60000 | ||
24-core 96000 MB | 72000 | ||
16-core 128000 MB | 60000 | ||
32-core 128000 MB | 80000 | ||
24-core 144000 MB | 76000 | ||
24-core 192000 MB | 80000 | ||
32-core 192000 MB | 90000 | ||
48-core 192000 MB | 120000 | ||
32-core 256000 MB | 100000 | ||
48-core 288000 MB | 140000 | ||
48-core 384000 MB | 140000 | ||
64-core 256000 MB | 150000 | 25–9000 GB | |
64-core 384000 MB | 150000 | ||
64-core 512000 MB | 150000 | 25–12000 GB | |
90-core 720000 MB | 150000 |
Note:
- When the local resources are sufficient, you can enable the QuickChange mode by turning on the QuickChange toggle on the configuration adjustment page in the console.
- In some cases, instance restart is not required in the QuickChange mode and the configuration adjustment will take effect immediately after you submit the request, as shown below:
You can adjust the instance configuration using the UpgradeDBInstance
API. For more information, see UpgradeDBInstance.
It may be because the used storage capacity has reached the maximum capacity of the hard disk. To downgrade your instance, you need to clean up data first and make sure the remaining available capacity accounts for more than 20% of the total capacity or over 50 GB.
It may be because you select During maintenance time as the Switch Time when you adjust instance configuration in the console, so the instance will not be switched immediately after the adjustment.
To switch immediately, you can locate the target instance in the instance list and click Switch Now in the Operation column. The switch causes a short disconnection lasting for just seconds. Ensure that your business has a reconnection mechanism.
The time it takes depends on the instance's data volume and the read requests to replicate data.
Instances can still be accessed during the upgrade, but a VIP switch causes a short disconnection lasting for just seconds after the upgrade completes.
You can view the progress in Task List in the console.
If over 85% disk space is used, we recommend you delete data no longer used or expand disk space in the console by selecting More > Adjust Configurations in the Operation column on the right of the instance list.
On the configuration adjustment page, if the QuickChange mode is supported, the QuickChange toggle can be turned on or off as needed; otherwise, the toggle cannot be used.
If the kernel minor version of the instance is not the latest when memory or disk capacity is expanded, it will be upgraded to the latest. In this case, enabling the QuickChange mode will cause the database restart.
The instance needs to be restarted in some cases. A prompt whether to restart the instance will be displayed on the configuration adjustment page as shown below:
Note:If the kernel minor version of the instance is the latest, adjusting only the disk capacity in the QuickChange mode will not cause the instance to restart.
You can check the QuickChange switch on the configuration adjustment page: if the switch is toggled on, the QuickChange mode is enabled; otherwise, the mode is disabled.
APIs do not support QuickChange for the time being, so instance configuration can be adjusted only by migrating data if you use APIs. APIs will support QuickChange in the future.
The innodb_buffer_pool_size
parameter will be modified according to the configuration changes.
It is the same as the normal mode. In the QuickChange mode, some parameters will be modified according to the configuration changes.
The QuickChange mode requires no data migration, so it takes less time to adjust instance configuration.
Was this page helpful?