Esta página aún no está disponible en su idioma local. Estamos trabajando arduamente para agregar más versiones de idiomas. Gracias por tu apoyo.
Distributed Message Service for RocketMQ
Distributed Message Service for RocketMQ
- What's New
- Function Overview
- Product Bulletin
- Service Overview
- Getting Started
-
User Guide
- Process of Using RocketMQ
- Creating a User and Granting DMS for RocketMQ Permissions
- Buying a RocketMQ Instance
- Configuring a Topic
- Accessing an Instance
- Managing Messages
- Managing Consumer Groups
-
Managing Instances
- Viewing and Modifying Basic Information of a RocketMQ Instance
- Viewing Background Tasks of a RocketMQ Instance
- Configuring Tags for a RocketMQ Instance
- Exporting RocketMQ Instances
- Diagnosing a RocketMQ Instance
- Restarting Brokers of a RocketMQ Instance
- Deleting a RocketMQ Instance
- Configuring SSL of a RocketMQ Instance
- Modifying RocketMQ Specifications
- Migrating Metadata
- Viewing Monitoring Metrics and Configuring Alarms
- Viewing RocketMQ Audit Logs
- Best Practices
- Developer Guide
- API Reference
- SDK Reference
- FAQs
- Videos
On this page
Show all
Help Center/
Distributed Message Service for RocketMQ/
User Guide/
Migrating Metadata/
RocketMQ Metadata Migration Overview
RocketMQ Metadata Migration Overview
Updated on 2024-12-25 GMT+08:00
RocketMQ metadata contains topics and consumer groups excluding message production or consumption records. To use the original topics and consumer groups, migrate their metadata to a specified RocketMQ instance, without the need of manual creation.
RocketMQ service migration involves the following scenarios:
- Migrating RocketMQ instance metadata from others, which includes:
- Metadata of others' RocketMQ
- Metadata of self-hosted RocketMQ instance
- Metadata of another cloud RocketMQ instance
- Migrating RocketMQ instance metadata from RabbitMQ
Parent topic: Migrating Metadata
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
The system is busy. Please try again later.