Upgrade the Nacos engine version

Before you begin

• Select an instance edition: Before upgrading, refer to the Instance Edition Selection Guide to decide whether to upgrade to the developer edition or the professional edition. For the billing details of each edition, see Billing Overview of Common Instances.

• Evaluate specifications: To ensure data consistency and a stable upgrade, MSE Nacos performs a doublewrite on registered service data during the process. Before you start, ensure that the number of provider instances in your cluster does not exceed the capacity of your basic edition specifications. This prevents the doublewrite from affecting your services. For more information, see Evaluate the Capabilities of Common Instances.

• Check the engine version: You can upgrade a basic edition instance to the professional or developer edition only if your Nacos engine is version 1.2.1.0 or later. If you are using a 1.1.3.x version, you must first upgrade to version 1.2.1 and then upgrade the instance edition. For instructions, see Upgrade the Nacos engine version.

• Review engine version compatibility: For information about the features of different MSENacos engine versions, see Nacos engine versions. For system stability, we recommend that you avoid using restricted Nacos SDK versions. To understand the reasons and find solutions, see Restricted Nacos SDK versions.

• Eureka engine: The MSE-managed Eureka service has been discontinued. MSE Nacos supports the Eureka protocol and is compatible with Eureka clients. We recommend migrating your Eureka basic edition instances to MSE Nacos professional or developer edition instances.

Upgrade impact

• The upgrade takes about 10 minutes. During this time, you cannot perform any operations on the instance in the console. We recommend performing the upgrade during off-peak hours to avoid disrupting your services.

• For instances with three or more nodes, the upgrade uses a rolling deployment across the nodes with automatic data synchronization. This ensures a zero-downtime upgrade.

• Instances with one or two nodes are not high availability instances, so the upgrade will cause downtime.

• The upgrade process is designed to be seamless for your services. However, network reconnections may occur, generating reconnection logs. Monitoring data may also show temporary fluctuations due to the cluster restart.

• When upgrading from a Eureka engine to the Nacos professional or developer edition:

  • You do not need to modify your application code.

  • Network reconnections during the upgrade may cause heartbeat renewal to fail for a small number of registered instances. The Eureka client will automatically retry the registration during its next renewal cycle and will recover after connecting to a healthy server node.

  • By default, a Eureka basic edition instance is migrated to the Nacos developer or professional edition with engine version 2.1.2.2. You can later upgrade to the latest Nacos version. For more information, see Upgrade the Nacos engine version.

Upgrade path

You can upgrade from the basic edition to the professional or developer edition only if your Nacos engine is version 1.2.1.0 or later. If you are using a 1.1.3.x version, you must first upgrade the engine to version 1.2.1. For instructions, see Upgrade the Nacos engine version.

Upgrade the Nacos engine version

1. Log on to the MSE console, and select a region in the top navigation bar.

2. In the left-side navigation pane, choose Microservices Registry > Instances.

3. You can start the upgrade from the console in one of two ways:

   Note

   If the target instance is already the latest version, the Manual Upgrade option is not displayed.

   Method 1

   On the Instances page, find the target instance and click Manual Upgrade in the Engine Version column.

   Method 2

   On the Instances page, click the instance you want to upgrade. On the Basic Information page, click Manual Upgrade next to Engine Version.

4. In the Cluster Upgrade dialog box, click OK.

Upgrade the Nacos/Eureka basic edition

1. Log on to the MSE console, and select a region in the top navigation bar.

2. On the Instances page, find the MSE instance, and click More in the Actions column.

   • For a subscription instance, select Upgrade or Downgrade based on your business requirements.

   • For a pay-as-you-go instance, select Upgrade/Downgrade.

3. On the change specifications page, select a Product Edition:

   • For single-node instances, select Developer edition.

   • For multi-node instances, select Professional edition.

   Important

   The following limitations apply when you change the Product Edition:

   • A Basic Edition instance can be upgraded to the Developer Edition or Professional Edition.

   • A Developer Edition instance can only be upgraded to a later version of the Developer Edition. It cannot be upgraded to the Professional Edition.

   • A Professional Edition instance can only be upgraded to a later version of the Professional Edition. It cannot be downgraded to the Developer Edition.

4. Confirm the Engine specification and Number of Cluster Nodes. After you verify the total cost in the lower-right corner, click Buy now.

FAQ

<dependency>
    <groupId>com.alibaba.cloud</groupId>
    <artifactId>spring-cloud-starter-alibaba-nacos-discovery</artifactId>
    <version>${springcloudalibaba.version}</version>
    <exclusions>
        <exclusion>
        <groupId>com.alibaba.nacos</groupId>
        <artifactId>nacos-client</artifactId>
         </exclusion>
    </exclusions>
</dependency>
<dependency>
    <groupId>com.alibaba.cloud</groupId>
    <artifactId>spring-cloud-starter-alibaba-nacos-config</artifactId>
    <version>${springcloudalibaba.version}</version>
    <exclusions>
        <exclusion>
            <groupId>com.alibaba.nacos</groupId>
            <artifactId>nacos-client</artifactId>
        </exclusion>
    </exclusions>
</dependency>
<dependency>
    <groupId>com.alibaba.nacos</groupId>
    <artifactId>nacos-client</artifactId>
    <version>2.0.2</version>
</dependency>

<dependency>
    <groupId>org.apache.dubbo</groupId>
    <artifactId>dubbo-registry-nacos</artifactId>
    <version>${dubbo.version}</version>
    <exclusions>
        <exclusion>
            <groupId>com.alibaba.nacos</groupId>
            <artifactId>nacos-client</artifactId>
        </exclusion>
    </exclusions>
</dependency>
<dependency>
    <groupId>com.alibaba.nacos</groupId>
    <artifactId>nacos-client</artifactId>
    <version>2.0.2</version>
</dependency>