Solution

Updated on 2025-02-12 GMT+08:00

View PDF

Introduction

This section describes a registry center migration solution based on Nacos Sync. This solution is applicable to users who build Nacos on Huawei Cloud.

Nacos Sync is an open-source component that supports bidirectional synchronization and smooth migration of the registry center. You can migrate services through synchronization tasks. Nacos Sync can synchronize the service information of the source cluster with that of CSE Nacos, in this way, the self-built registry center and CSE Nacos can be smoothly migrated, which is applicable to users who need service continuity.

NOTE:

Nacos Sync supports open-source Nacos 1.4.1 to 2.1.0.

As shown in the figure, you can use the Nacos Sync component to synchronize the service instances registered and subscribed to on the self-built Nacos to CSE Nacos in real time, implementing bidirectional registry of service instances.

Prerequisites

Create a CSE Nacos instance as the destination for self-built Nacos migration. For details, see Creating a Registry/Configuration Center.
Create a MySQL instance, database, and table because Nacos Sync depends on MySQL for deployment when Nacos Sync is used for synchronous migration. Create a pay-per-use general-purpose MySQL 5.7 instance with 2 vCPUs and 4 GB memory by referring to Buying an RDS for MySQL DB Instance. Modify the security group configuration to enable all ports by referring to Changing a Security Group
Create a pay-per-use x86 ECS with 4 vCPUs and 8 GB memory and EulerOS-EulerOS 2.9 64bit public image by referring to Purchasing a Custom ECS. Bind an EIP to the network configuration by referring to Binding an EIP. Use the same security group as MySQL and install JRE 8 on the ECS.
Synchronization tasks require bidirectional network interconnection. Therefore, your self-built Nacos, CSE Nacos, MySQL, and ECS must be in the same network segment and can communicate with each other. In addition, you have configured the security group rule by referring to Configuring Security Group Rules.