If the current instance specifications cannot meet your business needs, you can upgrade them in the console.
Note:
You can upgrade the peak bandwidth, disk capacity, partition count, and other instance specifications in the console. The specification upgrade is a smooth upgrade, so it won't interrupt your business.
New ports may be added during the upgrade. You can view them by clicking View All IPs and Ports in the Access Mode section on the instance details page later. When configuring the security group, you need to open all these ports.
Prerequisites
You need to check the following before the upgrade:
1. Check whether the instance has unavailable public network routes, supporting networks, and VPC networks. For more information, see Adding Routing Policy.
2. Check whether the instance has unsynced replicas. For more information, see Viewing Topic.
3. Check whether the instance has unfinished tasks (data migration), abnormally created topics, or abnormally deleted topic data.
Note:
If there are unfinished tasks, we recommend that you wait for all the tasks to be completed before the upgrade. If task execution is abnormal, submit a ticket for assistance.
Directions
Scenario 1: Upgrading Standard Edition instance specification
Scenario 2: Upgrading Standard Edition to Pro Edition
Scenario 3: Upgrading Pro Edition instance specification
2. On the instance list page, select More > Upgrade in the Operation column to enter the upgrade page.
3. Select Pro Edition as the target specification type.
Product Specs: Select a model based on the peak bandwidth and disk capacity.
Instance Price: You need to pay for the upgrade based on the number of days.
Rebalancing Time:
If the backend detects that data migration is required during the upgrade, you can choose to upgrade right away or at the specified time (upgrade at night is recommended to reduce the impact on your business). The estimated upgrade duration is calculated by backend APIs.
If the backend detects that data migration is not required during the upgrade, you will see the message "Rebalancing will not occur during the upgrade".
Upgrade Mode: If the backend detects that instance migration is required during the upgrade, you can select an upgrade mode as needed. Otherwise, you do not need to select an upgrade mode.
Stable: CKafka will limit the speed of data migration during the upgrade to ensure that instances have optimal bandwidth performance. This option is recommended if you do not want to affect business operations.
High-speed: CKafka will not limit the speed of data migration during the upgrade, thus affecting the bandwidth available for data production and consumption of instances. This option is recommended for off-peak hours or when service suspension is allowed.
4. Click Submit to complete the instance upgrade. You can view the upgrade progress in the Status column.
5. If you choose to upgrade at the specified time, you can modify the time you specified in the Status column.
2. On the instance list page, select More > Upgrade in the Operation column to enter the upgrade page.
3. Select the target specification for the instance.
Product Specs: Select a model based on the peak bandwidth and disk capacity.
Instance Price: You need to pay for the upgrade based on the number of days.
Rebalancing Time:
If the backend detects that data migration is required during the upgrade, you can choose to upgrade right away or at the specified time (upgrade at night is recommended to reduce the impact on your business). The estimated upgrade duration is calculated by backend APIs.
If the backend detects that data migration is not required during the upgrade, you will see the message "Rebalancing will not occur during the upgrade".
Upgrade Mode: If the backend detects that instance migration is required during the upgrade, you can select an upgrade mode as needed. Otherwise, you do not need to select an upgrade mode.
Stable: CKafka will limit the speed of data migration during the upgrade to ensure that instances have optimal bandwidth performance. This option is recommended if you do not want to affect business operations.
High-speed: CKafka will not limit the speed of data migration during the upgrade, thus affecting the bandwidth available for data production and consumption of instances. This option is recommended for off-peak hours or when service suspension is allowed.
4. Click Submit to complete the instance upgrade. You can view the upgrade progress in the Status column.
5. If you choose to upgrade at the specified time, you can modify the time you specified in the Status column.
Possible Causes of Upgrade Failures
1. The disk resources in the current AZ cannot meet the requirements of this upgrade. We recommend that you contact the Tencent Cloud customer service to check whether there are sufficient resources.
2. If the high-speed mode is selected during the instance upgrade, and there are bandwidth-intensive production tasks in the cluster, the data migration delay will increase. You can view monitoring data to see whether there are excessive peaks of production and consumption traffic during the upgrade. For more information, see Viewing Monitoring Data.
3. The upgrade process takes too long. The maximum message size configured for the broker to be migrated is 8 MB, while the size configured for the target broker is 1 MB. In this case, the target cluster cannot receive the oversized messages, causing the data migration failure and prolonging the upgrade duration. You can submit a ticket for assistance.
4. During the cluster upgrade or migration process, an exception may occur while updating the broker IP, causing the failure to pull the broker IP data of the new cluster. You can observe that no monitoring data is displayed for a period of time. You can submit a ticket for assistance. For more information, see Viewing Monitoring Data.
Yes
No
Was this page helpful?