Microservices Engine:Migrate Dubbo applications from a self-managed ZooKeeper registry to an MSE ZooKeeper 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 ZooKeeper instance, MSE Sync, and MSE ZooKeeper instance are interconnected.

Specifications

Procedure

Step 1: Create a migration task

1. In the left-side navigation pane of the MSE Sync tool, click Cluster Configuration. Then, click Add Cluster. In the Add Cluster dialog box, add the information about the source ZooKeeper instance, and click OK.

   Parameter	Description
   Cluster Name	Enter a name of the instance.
   Cluster Type	Select ZK.
   Cluster IP	Enter one or more combinations of an IP address and port number of the ZooKeeper instance. Each combination occupies one line. The default port number is 2181. Example: 127.0.0.1:2181 127.0.0.2:2181 127.0.0.3:2181 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 ZooKeeper instance.

   • Cluster Type: Select ZK.

   • Cluster IP Address List: Enter one or more combinations of an endpoint and service port number of the MSE ZooKeeper instance. Example: mse-8b7de****-p.zk.mse.aliyuncs.com:2181.

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

   • Group Name: If you want to synchronize multiple applications, you can leave this parameter empty. Otherwise, you must enter a specific Dubbo group name.

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, click Data Management > Znode Management. Check whether services exist in the default Dubbo path.

Step 3: Migrate the Dubbo client

1. Change the endpoint of the Dubbo client.

   Find the XML configuration file of the Dubbo client and replace the endpoint of the self-managed ZooKeeper instance in dubbo:registry address with the endpoint of the MSE ZooKeeper instance. The following code provides an example.

   Before the change:

    <dubbo:registry address="zookeeper://127.0.0.1:2181"/>

   After the change:

    <dubbo:registry address="zookeeper://mse-8b7de****-p.zk.mse.aliyuncs.com:2181"/>

2. Restart the Dubbo client to connect the client to the MSE ZooKeeper instance.

   Note

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

Step 4: Shut down the self-managed ZooKeeper instance

1. Shut down the self-managed ZooKeeper instance.

2. Disable the MSE Sync tool.