
Instance Architecture | Disk Type | Adjustment Item | Adjustment Decision | Adjustment Impact | Time |
Single-node instance (formerly basic edition) | Cloud disk | Specification upgrade or disk capacity expansion or specification downgrade | Upgrade and downgrade | Disk capacity expansion: 1. The instance will perform in-place capacity expansion during the configuration adjustment. 2. During this period, no instance restart or momentary disconnection will occur, and the business will not be affected. 3. You can set the effective time, which will not affect businesses. The time is the actual configuration change time. Upgrade or downgrade of the instance specifications: 1. The instance will be restarted during configuration adjustment. 2. The service will be unavailable for about 1 to 3 minutes. 3. Perform the adjustment during off-peak hours. | You need to select the time to take effect. |
Two-node instance (formerly high-availability edition) | Local disk | Disk capacity reduction | Downgrade | 1. The instance disk capacity will be reduced during the configuration adjustment. 2. Data migration and instance restart will not be performed, and no momentary disconnections will occur. 3. You can custom the effective time that is also the adjustment time without affecting the business. | You need to select the time for the new configuration to take effect |
| | Specification downgrade | Downgrade | 1. The instance specification will be downgraded during configuration adjustment. 2. The service will become unavailable for around 1 minute. 3. Perform the adjustment during off-peak hours. | You need to select the time to take effect. |
| | Specification upgradeordisk capacity expansion | Migration and upgrade | 1. Data migration will be involved during the instance configuration adjustment, and the larger the data volume, the longer the data migration time. Access to the instance will not be affected during this period. 2. A switch will be performed after migration is completed, which causes a momentary disconnection from the database for few seconds. Make sure that your business has a reconnection mechanism. 3. Most database, account, and network operations are unavailable during the momentary disconnection. Therefore, we recommend that you perform the switch during off-peak hours. | You need to select the time to take effect. |
| | Specification upgrade or disk capacity expansion | Upgrade | 1. The instance specification or disk capacity will be upgraded or expanded during configuration adjustment. 2. Data migration and instance restart will not be performed, and no momentary disconnections will occur. 3. You can customize the effective time that is also the adjustment time without affecting the business. | You need to select the time for the new configuration to take effect |
Two-node instances (formerly high-availability edition) | Cloud disk | Specification upgrade or disk capacity expansionorspecification downgrade | Migration, upgrade, and downgrade | Disk capacity expansion: 1. The instance will perform in-place capacity expansion during the configuration adjustment. 2. Instance restart or momentary disconnection will not occur during this period. 3. You can set the effective time, which will not affect businesses. The time is the actual configuration change time. Upgrade or downgrade of the instance specifications: 1. The instance will be restarted during configuration adjustment. 2. The service will be unavailable for about 1 to 3 minutes. 3. Perform the adjustment during off-peak hours allowed by the business. | You need to select the time to take effect. |
Multi-node | Cloud disk | Specification upgrade, disk capacity expansion, or specification downgrade | Upgrade, expand, or downgrade | Disk capacity expansion: 1. The instance will perform in-place capacity expansion during the configuration adjustment. 2. Instance restart or momentary disconnection will not occur during this period. 3. You can set the effective time, which will not affect businesses. The time is the actual configuration change time. Upgrade or downgrade of the instance specifications: 1. The instance will be restarted during configuration adjustment. 2. The service will be unavailable for about 1 to 3 minutes. 3. Perform the adjustment during off-peak hours allowed by the business. | You need to select the time for the new configuration to take effect. |
Instance Architecture | Disk Type | Adjustment Item | Adjustment Decision | Adjustment Impact | Time |
Single-node instance (formerly basic edition) | Cloud disk | Disk capacity expansion + specification upgrade or downgrade | Upgrade and downgrade | 1. The instance will be restarted during configuration adjustment. 2. The service will be unavailable for about 1 to 3 minutes. 3. Perform the adjustment during off-peak hours. | You need to select the time to take effect. |
Two-node instance (formerly high-availability edition) | Local disk | Specification upgrade + disk capacity expansion | Upgrade | 1. The instance specification or disk capacity will be upgraded or expanded during configuration adjustment. 2. Data migration and instance restart will not be performed, and no momentary disconnections will occur. 3. You can custom the effective time that is also the adjustment time without affecting the business. | You need to select the time for the new configuration to take effect |
| | Specification upgrade + disk capacity expansion | Migration and upgrade | 1. Data migration will be involved during the instance configuration adjustment, and the larger the data volume, the longer the data migration time. Access to the instance will not be affected during this period. 2. A switch will be performed after migration is completed, which causes a momentary disconnection from the database for few seconds. Make sure that your business has a reconnection mechanism. 3. Most database, account, and network operations are unavailable during the momentary disconnection. Therefore, we recommend you perform the switch during off-peak hours. | You need to select the time to take effect. |
| | Specification upgrade + disk capacity reduction | Upgrade and downgrade | 1. The instance specification will be upgraded and the disk capacity will be reduced during configuration adjustment. 2. Data migration and instance restart will not be performed, and no momentary disconnections will occur. 3. The time to take effect (i.e., the time when the configuration adjustment will occur) can be customized without affecting the business. | The time to take effect can be customized. |
| | Specification upgrade + disk capacity reduction | Migration, upgrade, and downgrade | 1. Data migration will be involved during the instance configuration adjustment, and the larger the data volume, the longer the data migration time. Access to the instance will not be affected during this period. 2. A switch will be performed after migration is completed, which causes a momentary disconnection from the database for few seconds. Make sure that your business has a reconnection mechanism. 3. Most database, account, and network operations are unavailable during the momentary disconnection. Therefore, we recommend you perform the switch during off-peak hours. | You need to select the time to take effect. |
| | Specification downgrade + disk capacity expansion | Upgrade and downgrade, or migration, upgrade, and downgrade | 1. The service may become unavailable for around 1 minute, and data migration may be involved during the instance configuration adjustment, and the larger the data volume, the longer the data migration time. Access to the instance will not be affected during this period. 2. A switch will be performed after migration is completed, which causes a momentary disconnection from the database for few seconds. Make sure that your business has a reconnection mechanism. 3. Most database, account, and network operations are unavailable during the momentary disconnection. Therefore, we recommend you perform the switch during off-peak hours. | You need to select the time to take effect. |
| | Specification downgrade + disk capacity reduction | Downgrade | 1. The instance specification will be downgraded during configuration adjustment. 2. The service will become unavailable for around 1 minute. 3. Perform the adjustment during off-peak hours. | You need to select the time to take effect. |
Two-node instance (formerly high-availability edition) | Cloud disk | Disk capacity expansion + specification upgrade or downgrade | Upgrade, expand, or downgrade | 1. The instance will be restarted during configuration adjustment. 2. The service will be unavailable for about 1 to 3 minutes. 3. Perform the adjustment during off-peak hours allowed by the business. | You need to select the time to take effect. |
Multi-node | Cloud disk | Disk capacity expansion + specification upgrade or downgrade | Upgrade, expand, or downgrade | 1. The instance will be restarted during configuration adjustment. 2. The service will be unavailable for about 1 to 3 minutes. 3. Perform the adjustment during off-peak hours allowed by the business. | You need to select the time for the new configuration to take effect. |


API | Description |
This API is used to pre-check the impact of the instance configuration adjustment before the adjustment. | |
This API is used to upgrade an instance. | |
This API is used to complete the instance upgrade and switch immediately without waiting for the maintenance window when the instance status is "upgrade pending switch" after scale-out is initiated. This API needs to be called during off-peak hours of the instance. Some databases cannot be accessed before the switch is completed. |
Feedback