Product Functions
This section describes main functions of DMS for RocketMQ. You can check if a certain function is available in a region on the console.
Purchasing a RocketMQ Instance
Before using DMS for Kafka, you must purchase a Kafka instance. RocketMQ instances are physically isolated and exclusively occupied by each tenant. For details, see Buying a RocketMQ Instance.
Connecting to a RocketMQ Instance
Connect to a RocketMQ instance before using an open-source RocketMQ client to produce and consume messages.
When you purchase a RocketMQ instance, the available encryption mode is SSL. For details, see Accessing an Instance.
Managing Topics
A topic is the basic unit for sending and receiving messages. After purchasing a RocketMQ instance, you must manually create topics before producing and consuming messages. For details, see Creating a RocketMQ Topic.
Changing Instance Specifications
After creating a RocketMQ instance, you can expand its storage space and broker or instance flavor, and increase the number of brokers. They can only be changed separately. For details, see Modifying RocketMQ Specifications.
Public Network Access
To access a RocketMQ instance over a public network, enable public access and configure EIPs for the instance.
You can change the public access setting only when the RocketMQ instance is in the Running state. For details, see Configuring Public Access for a RocketMQ Instance.
Message Query
View the content of a message and check whether the message is successfully produced or consumed.
DMS RocketMQ messages can be queried by topic, message ID, or message key. For details, see Viewing RocketMQ Messages.
Managing Consumer Groups
A consumer group is a group of consumers with the same behavior and is used to manage and maintain message consumption. For details, see Managing Consumer Groups.
Managing Users
RocketMQ instances support ACL-based permission control. You can create multiple users and assign different topic and consumer group permissions to them. For details, see Configuring RocketMQ ACL Users.
Dead Letter Queue
Dead letter queues store messages that cannot be correctly consumed.
If a message fails to be consumed, the system will retry sending it. After the maximum number of retries (which is 16 by default and configurable on the client) is reached and the message consumption still fails, the message becomes a dead letter message and is delivered to the dead letter queue that corresponds to the consumer.
DMS for RocketMQ supports querying, exporting, and resending dead letter messages. For details, see Managing RocketMQ Dead Letters.
Instance Diagnosis
You can diagnose an instance to quickly locate faults when message consumption is slow or fails. For details, see Diagnosing a RocketMQ Instance.
Sending and Receiving Messages
You can access the instance by using an open-source RocketMQ client to produce and consume messages. For more information, see Overview.
Scheduled Messages
DMS for RocketMQ supports message scheduling at any time. For v4.8.0, it can be scheduled up to one year later. For v5.x, it can be scheduled up to seven days later. The scheduling can be canceled.
Scheduled messages: After being sent from producers to DMS for RocketMQ, messages are delivered to consumers only after a specified time point. For details, see Delivering Scheduled Messages.
Tags
Tags facilitate RocketMQ instance identification and management.
Tags can be added in instance creation, or on the instance details page. For details, see Configuring Tags for a RocketMQ Instance.
Monitoring
Cloud Eye monitors RocketMQ instance metrics in real time. You can view these metrics on the console. For details, see Viewing Monitoring Metrics and Configuring Alarms.
Audit
RocketMQ operations are recorded by Cloud Trace Service (CTS), which is a log audit service provided by Huawei Cloud. CTS collects, stores, and queries records of operations on RocketMQ instances, facilitating security analysis, compliance audit, resource tracking, and fault locating. For details, see Viewing RocketMQ Audit Logs.
API
DMS for RocketMQ provides REST APIs that support HTTP/HTTPS methods. You can call APIs to create, delete, and modify instances. For more information, see API Overview.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot