Release Notes
Announcements
Parameter | Description |
Current Cluster | Cluster to which a group belongs, which cannot be modified. |
Group Name | Name of a group, which cannot be modified after creation. The name should comply with naming rules: The name must be 3 to 100 characters in length and can contain only letters, digits, percent signs (%), hyphens (-), and underscores (_). |
Tag | Tags are used to categorize and manage group resources. You can also grant sub-accounts read/write permissions for specific resource types through authorization by tag. For details, see Configuring Resource Tags and Granting Tag-Level Permissions to Sub-accounts. |
Group Description | Enter the group description, with up to 128 characters. |
Max Retries | Maximum number of times that a message can be redelivered. If a message still fails to be consumed successfully after the maximum number of retries has reached, it will be delivered to a dead letter queue or discarded. If you use a TDMQ for RocketMQ 4.x client, the number of message retries set on the client prevails. If you use a RocketMQ 5.x client, the number of message retries set on the page prevails. |
Delivery Sequence | Sequence in which the server delivers messages to the consumer for consumption. Sequential delivery and concurrent delivery are supported, and concurrent delivery is the default method. Sequential delivery: Messages that are associated logically are delivered to the same queue for serialized processing. This ensures that messages are consumed strictly in the sequence they were sent. Concurrent delivery: Messages are delivered to multiple queues for parallel processing by multiple consumer threads. This maximizes system throughput and resource utilization, but cannot guarantee the message processing sequence. |
Enable Consumption | After it is disabled, all consumption operations under a group are suspended. Re-enabling it can resume consumption. It can be used for system Ops, consumer group flow control, and fault isolation, achieving cluster-level protection and smooth operations. |
Parameter | Description |
Current Cluster/Namespace | Cluster or namespace to which a group belongs, which cannot be modified. |
Group Name | Name of a group, which cannot be modified after creation. The name should comply with naming rules: The name must be 3 to 83 characters in length and can contain only letters, digits, percent signs (%), hyphens (-), and underscores (_). |
Protocol Type | TDMQ for RocketMQ supports access using Transmission Control Protocol (TCP) and Hypertext Transfer Protocol (HTTP). It is recommended that you create a group for each protocol. If multiple consumers use the same group to consume messages, with certain consumers using the TCP protocol and others using the HTTP protocol, it may lead to consumption failures, message duplication, or message loss. |
Tag | Tags are used to categorize and manage group resources. You can also grant sub-accounts read/write permissions for specific resource types through authorization by tag. For details, see Configuring Resource Tags and Granting Tag-Level Permissions to Sub-accounts. |
Group Description | Enter the group description, with up to 128 characters. |
Enable Consumption | After it is disabled, all consumption operations under a group are suspended. Re-enabling it can resume consumption. It can be used for system Ops, consumer group flow control, and fault isolation, achieving cluster-level protection and smooth operations. |
Enable Broadcasting | After it is disabled, all consumers declared in the broadcast mode under the group are paused. Re-enabling it can resume consumption. Clustering consumption: In the clustering consumption mode, each message only needs to be processed by any of the consumers in the cluster. Broadcasting consumption: In the broadcasting consumption mode, each message is pushed to all registered consumers in the cluster to ensure that the message is consumed at least once by each consumer. |
Was this page helpful?
You can also Contact sales or Submit a Ticket for help.
Help us improve! Rate your documentation experience in 5 mins.
Feedback