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 or professional edition. For billing details, see Billing Overview of Common Instances.

• Evaluate specifications: During the upgrade, MSE Nacos performs a doublewrite on registered service data to ensure data consistency and upgrade stability. Before you begin, ensure that the provider instance count in your cluster does not exceed the maximum instance count for the basic edition of the corresponding specifications, to avoid the doublewrite impacting your services during the upgrade. 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 details about MSE Nacos engine version features, see Nacos engine versions. For system stability, we recommend avoiding restricted Nacos SDK versions. For the reasons and 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.

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 rolling deployment across nodes with automatic data synchronization, ensuring a zero-downtime upgrade.

• For most services, the upgrade is lossless. However, network reconnections during the upgrade may generate some reconnection and access error logs. This is expected behavior. Monitoring data may also show brief fluctuations due to the cluster restart.

• In some special scenarios, a lossless upgrade may not be guaranteed. Before performing an upgrade, check for the following conditions:

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

  • If you are using an older client version, there is a very low probability that packet loss or other unknown anomalies during the upgrade may trigger a client bug, causing your services to go offline. In this case, the upgrade will cause downtime.

  • If you are using a lower version of Spring Cloud Alibaba and have configured the Spring Cloud Actuator health check path as the liveness or readiness probe for your service, due to a bug in older Spring Cloud Alibaba versions, there is a very low probability that probe failure could cause your application to restart automatically. In this case, the upgrade will cause downtime.

• 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. Eureka clients automatically retry registration at their next renewal and 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>