Migrating Nacos and ZooKeeper, with new tools

Author: Zikui

background

There are two main schemes for registry migration in the industry, one is dual registration and dual subscription mode (similar to database double writing), and the other is Sync mode (similar to database DTS); MSE supports both modes at the same time, for opening MSE service management For customers, the MSE service management agent can help users perform dual registration and dual subscription smooth migration; for those without MSE service management available, one-click migration can be done through the MSE Sync tool we launched today.

What is MSE Sync

MSE Sync is a data synchronization tool based on the deep optimization of open source NacosSync. MSE Sync provides two-way synchronization, automatic service acquisition, one-click synchronization of all services and other capabilities to help users better complete the migration of Nacos and Zookeeper registration configuration centers. MSE Sync can synchronize the service information in the user source cluster with the service information in the MSE cloud products during the user migration process, so as to realize the smooth migration of users between the self-built configuration registry and MSE products.

In order to avoid the inconsistency of service information at both ends caused by the downtime of a single instance, MSE Sync can implement disaster recovery by deploying multiple instances.

MseSync is adapted to the service registration logic of Zookeeper and Nacos, and can realize the synchronization of service information from Zookeeper to Zookeeper, Zookeeper to Nacos, and Nacos to Nacos (more synchronization capabilities are being improved), and supports automatic acquisition of service information from Zookeeper and Nacos, One-click selection to avoid tedious operations.

How to migrate to the cloud through MSE Sync

First, purchase an instance of the corresponding specification and an MSE Sync host of the corresponding specification from MSE according to the business scale. For the instance specification, please refer to the relevant documents at the end of the article. Zookeeper and Nacos have development and professional versions for development, testing and production environments. The professional version supports many AZ deployment is more stable. It is recommended to use the professional version in the production environment. After MSE Sync is deployed, it is recommended to deploy at least two MSE Sync instances for production environment migration to ensure disaster tolerance. MSE Sync requires database resources, so prepare the Mysql database in advance.

After the migration environment is ready, you can add cluster information and synchronization information in MSE Sync. MSE Sync provides a white screen operation, supports automatic pulling of the corresponding cluster service information, automatically synchronizes the instances registered in the service, and simplifies the operation process.

Taking Zookeeper to migrate Zookeeper as an example, the synchronization process is generally as follows:

First, add the source cluster and target cluster information in MSE Sync, as follows:

Then add a new synchronization to the service synchronization. After selecting the source cluster and synchronization type (if the synchronization type is service information), MSE Sync will automatically pull the service information in the source cluster. You can select all and synchronize all with one click. After the service is determined, the service information will be bidirectionally synchronized between the source cluster and the target cluster.

After confirming that the service information has been synchronized to the target cluster, the application migration can be performed.

In the migration process of the application, the configuration information can be updated in batches according to the dependencies of each module of the business and the core level of the modules, thereby improving the smoothness of the migration process.

If the multi-instance MSE Sync goes down during the synchronization process, the service information will be synchronized through other MSE Sync instances to ensure the integrity and real-time of the service information in the source cluster and the target cluster. In this case, only the downed MSE needs to be restarted. Sync can be added to the synchronization process, and the joining process will not affect the existing synchronization process.

Nacos Migration Nacos reference documentation:

https://help.aliyun.com/document_detail/445140.html

Zookeeper migration Nacos reference documentation:

https://help.aliyun.com/document_detail/446904.html

Advantages of MSE over self-built

MSE's Zookeeper/Nacos provides core competencies such as high availability, high performance, security and ease of use.

Product experience address:

https://www.aliyun.com/product/aliware/mse

---

99 Promotion

New customers receive 30% off the annual package and 20% off the monthly package. Welcome to try it out. If you have any questions, please scan the DingTalk QR code (34754806) to communicate with us~

MSE cloud native gateway prepaid, MSE registered configuration prepaid first purchase 20% off, first purchase 1 year and above 30% off. Click here to take advantage of the discount!