Microservices Engine:Migrate applications from a self-managed Eureka registry to an MSE Nacos registry

Limits

• If the MSE Sync tool breaks down, the synchronization service is interrupted. Therefore, we recommend that you deploy the MSE Sync tool on at least two nodes. After the migration process starts, you must complete the migration at the earliest opportunity.

• The networks among the self-managed Eureka instance, MSE Sync, and MSE Nacos instance are interconnected.

Procedure

Step 1: Create a migration task

1. In the left-side navigation pane of the MSE Sync tool, click Cluster Configuration. On the page that appears, click Add Cluster. In the Add Cluster dialog box, add the information about the source Eureka instance, and click OK.

   Parameter	Description
   Cluster Name	Enter a name of the instance.
   Cluster Type	Select EUREKA.
   Cluster IP Address List	Enter one or more combinations of an IP address and port number of the source Eureka instance. Each combination occupies one line. The default port number is 8761. If the source instance uses a Server Load Balancer (SLB) instance for load balancing, enter the IP address and port number of the SLB instance.

2. Click Add Cluster again to add the information about the destination Nacos instance.

   Parameter	Description
   Cluster Name	Enter a name of the instance.
   Cluster Type	Select Nacos.
   Namespace	The default namespace is public.
   Username	If Nacos authentication is enabled, enter the username and password.
   Password
   Cluster IP Address List	Enter one or more combinations of an endpoint and service port number of the destination Nacos instance. The default port number is 8848. Example: mse-xxxxxxx-p.nacos-ans.mse.aliyuncs.com:8848.

3. In the left-side navigation pane, click Service Synchronization. On the page that appears, click New Sync. In the New Sync dialog box, add the applications that you need to migrate.

   • Sync Mode: Select Bidirection. In this mode, data can be synchronized between the source and destination instances if data on the source or destination instance updates.

   • Sync Type: Select Service Information. MSE Sync automatically displays all applications that are registered with the source instance. You can select the applications based on your business requirements.

4. Click OK.

   The synchronized application names are displayed on the Service Synchronization page of the MSE Sync tool.

Step 2: Verify the synchronization result

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. On the Instances page, click the name of the instance.

4. In the left-side navigation pane, choose Service Management > Services.

Step 3: Migrate the client

1. Replace the endpoint of the self-managed Eureka instance with the endpoint of the MSE Nacos instance.

2. Restart the client to connect the client to the MSE Nacos instance.

   Note

   To ensure business continuity, we recommend that you restart clients in batches. After the restart is complete, check whether all clients are connected to the MSE Nacos instance.

Step 4: Shut down the self-managed Eureka instance

1. Shut down the self-managed Eureka instance.

2. Stop the MSE Sync tool.