tencent cloud

Feedback

Upgrading Instance

Last updated: 2022-06-17 17:07:04

    Overview

    If the current instance specifications cannot meet your business needs, you can upgrade them in the console.

    Note:

    The instance specifications you can upgrade include peak bandwidth, disk capacity, and the number of topics/partitions. You can also increase the disk capacity only. The upgrade is smooth without suspending your services.

    Prerequisites

    Check the following items before upgrading:

    1. Check whether the instance has unavailable public network routes, supporting networks, VPC networks, etc. For more information, see Adding Routing Policy.
    2. Check whether the instance has unsynced replicas. For more information, see Topic Management.
    3. Check whether the instance has unfinished tasks (data migration), abnormally created topics, abnormally deleted topic data, etc.
      If there are unfinished tasks, we recommend you wait for all the tasks to be completed before upgrading. If task execution is abnormal, submit a ticket for assistance.

    Directions

    1. Log in to the CKafka console.
    2. In the Operation column on the instance list page, select More > Upgrade to enter the upgrade page.
    3. Select the target specification for the instance.
    4. Click Submit to complete the instance upgrade.

    Possible Causes of Upgrade Failures

    1. The disk resources in the current AZ cannot meet the requirements of this upgrade. We recommend you contact the Tencent Cloud customer service to check whether there are sufficient resources.
    2. If the high-speed mode is selected during instance upgrade, and there are production tasks that use a lot of bandwidth resources in the cluster, the data migration delay will increase. You can view the monitoring data to see whether there are excessive peaks of the production and consumption traffic during the upgrade.
    3. The upgrade process takes too long. The maximum acceptable message byte size of the migrated server configuration is 1 MB, but the broker configuration that needs to be migrated is 8 MB, so the broker cannot receive oversized message migration, resulting in prolonged data migration. Submit a ticket for assistance.
    4. During the upgrade or migration between the new and old clusters, the broker IP update is abnormal, causing the broker IP of the new cluster to fail to pull data. You can view the monitoring data to see that there is no monitoring data for a period of time. Submit a ticket for assistance.
    Contact Us

    Contact our sales team or business advisors to help your business.

    Technical Support

    Open a ticket if you're looking for further assistance. Our Ticket is 7x24 avaliable.

    7x24 Phone Support