Creating the Group

Last updated:2026-01-23 17:34:04

Creating the Group

Last updated: 2026-01-23 17:34:04

Scenarios
A group is used to identify a type of consumers who usually consume the same type of messages and use the same message subscription logic.
Constraints and Limitations
Users should create a group in the console before starting a consumer client.
The default ratio of topics to groups is 1:10. When the group quota in a cluster is insufficient, you can increase the group quota by increasing the topic quota. For specific operations, see Adjusting Cluster Specifications.
Operation Steps
1. Log in to the TDMQ for RocketMQ console.
2. In the left sidebar, select Group, select the region and target cluster, and click Create to go to the Create Group page.
3. Specify the group information.
5.x Clusters
4.x Clusters
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.
4. Click Submit to complete the creation of the group.

Was this page helpful?

You can also Contact Sales or Submit a Ticket for help.

Yes

Feedback

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.

tencent cloud

Scenarios

Constraints and Limitations

Operation Steps