Single-Write Multiple-Read Cluster Migration Solutions
Last updated:2025-12-24 15:00:42
Single-Write Multiple-Read Cluster Migration Solutions
Last updated: 2025-12-24 15:00:42
This document provides an overview of feasible solutions to the migration between different clusters. You can select a suitable migration solution based on your business scenario.
Scenarios
1. Migration cannot be performed at the virtual cluster level.
2. It is expected to migrate resources under a virtual cluster to different pro clusters.
3. A self-built Pulsar cluster needs to be migrated to a TDMQ for Apache Pulsar cluster.
Single-Write Multiple-Read Solution
The solution is overall simple, clear, and easy to operate. It does not cause data backlogs and achieves a smooth transition. With this solution, users can more flexibly control the resource granularity and grayscale method for the migration.
Migration Process
1. Start the business consumer connected to the access point of the new cluster (dual-read, with consumers consuming data from both the original cluster and the new cluster).
2. Change the access point addresses of the producers in the original cluster to those of the producers in the new cluster. Then, restart the producers to ensure that new messages are produced to the new cluster until all producers in the original cluster are modified/disabled (switch of the write operation, allowing the production traffic to be switched from the original cluster to the new cluster).
3. Pay attention to the message backlogs in the original cluster.
4. After you confirm that no backlogged messages remain in the original cluster, disable the consumers of the original cluster. In this case, the business has been migrated to the new cluster (single-read, where consumers only consume messages from the new cluster).
5. After the migration is completed, delete the original cluster.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No
Feedback