Microservices Engine:Upgrade a Nacos version

Preparations before an upgrade

• Select an edition: Before an upgrade, select Developer Edition or Professional Edition as the destination edition by referring to Select an instance type and an instance edition. For billing details of different editions, see Billing overview of common instances.

• Estimate specifications: To ensure the consistency of data and the stability of the upgrade process, MSE Nacos performs a doublewrite operation on the data of registered services during the upgrade. Before you upgrade the edition, you must make sure that the number of providers registered with the MSE instance is less than the maximum number of providers that are supported by the related specifications of Basic Edition. This prevents the negative impact of the doublewrite operation during the upgrade on your business. For more information, see Estimate the capabilities of common instances.

• Check the engine version: Only MSE engines that use Nacos 1.2.1.0 or later can be upgraded from Basic Edition to Professional Edition or Developer Edition. If your MSE engine uses Nacos 1.1.3.x, you must upgrade the version of the Nacos engine to 1.2.1 before you can upgrade the edition. For more information, see Upgrade a Nacos version.

• Engine version compatibility: For more information about the features that are supported by different editions of MSE Nacos engines, see Release notes for the MSE Nacos engine. To ensure system stability, we recommend that you do not use unrecommended versions of Nacos SDKs. For causes and solutions, see Application of MSE Nacos SDKs and unrecommended versions of Nacos SDKs.

• Eureka engine: The Eureka engine is no longer managed on MSE. MSE Nacos supports the Eureka protocol and is compatible with Eureka clients. We recommend that you migrate Eureka Basic Edition instances to MSE Nacos Professional Edition or Developer Edition instances.

Impact of an upgrade

• The upgrade process takes about 10 minutes. During an upgrade, you cannot perform operations on instances in the MSE console. We recommend that you perform upgrade operations during off-peak hours. This ensures the continuity of your business.

• For an instance that contains three or more nodes, a rolling deployment is performed for nodes, and data is automatically synchronized to these nodes during the upgrade. Your business is not interrupted during the upgrade.

• For an instance that contains one or two nodes, the instance cannot provide high availability, and your business may be interrupted during the upgrade.

• For business operations, upgrades do not cause interruptions but may re-establish network connections. As a result, connection re-establishment logs are generated and monitoring data fluctuates for a short period of time due to instance restarts.

• When you upgrade Eureka to Nacos Professional Edition or Development Edition:

  • You do not need to modify application code.

  • If the network is reconnected during the upgrade, heartbeat requests from a very small number of registered instances may fail. The Eureka client will automatically retry the registration during the next heartbeat request process and will automatically resume after it connects to a normal server node.

  • By default, the service engine version of Nacos Developer Edition or Professional Edition to which Eureka Basic Edition is migrated is 2.1.2.2. For more information about how to upgrade Nacos Developer Edition or Professional Edition to the latest version, see Upgrade a Nacos version.

Upgrade path

Only MSE engines that use Nacos 1.2.1.0 or later can be upgraded from Basic Edition to Professional Edition or Developer Edition. If your MSE engine uses Nacos 1.1.3.x, you must upgrade the version of the Nacos engine to 1.2.1 before you can upgrade the edition. For more information, see Upgrade a Nacos version.

Upgrade a Nacos 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. Use one of the following methods to perform an upgrade in the console:

   Note

   If the instance is of the latest version, Upgradeable is not displayed in the Engine version column of the instance.

   • Method 1: On the Instances page, find the desired instance and click Upgradeable in the Engine version column.

   • Method 2: On the Instances page, find the desired Nacos instance, click the icon in the Actions column. In the list that appears, select Upgrade.

   • Method 3: On the Instances page, click the name of the desired instance. On the Basic Information page, click Manual Upgrade next to Engine version.

4. In the Cluster Upgrade message, click OK.

Upgrade a Nacos or Eureka engine from Basic Edition to Professional Edition or Developer 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 page that appears, select an edition based on your business requirement.

   • For single-node instances, select Developer Edition.

   • For multi-node instances, select Professional Edition.

   Important

   When you change the product edition, take note of the following limits:

   • You can upgrade a Basic Edition instance to a Developer Edition instance or a Professional Edition instance.

   • You can upgrade a Developer Edition instance of an earlier version to a Developer Edition instance of a later version. You cannot upgrade a Developer Edition instance to a Professional Edition instance.

   • You can upgrade a Professional Edition instance of an earlier version to a Professional Edition instance of a later version. You cannot downgrade a Professional Edition instance to a Developer Edition instance.

4. Confirm the engine specifications, the number of nodes, and the amount in the lower-right corner of the page. Then, click Buy Now.

FAQ about upgrades

<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>