Release Notes and Announcements

Release Notes

Announcements

Product Introduction

Introduction and Selection of the TDMQ Product Series

What Is TDMQ for RocketMQ

Strengths

Scenarios

Product Series

Comparison with Open-Source RocketMQ

High Availability

Quotas and Limits

Supported Regions

Basic Concepts

Billing

Billing Overview

Pricing

Billing Examples

Pay-as-you-go Switch to Monthly Subscription (5.x)

Renewal

Viewing Consumption Details

Refund

Overdue Payments

Getting Started

Getting Started Guide

Preparations

Step 1: Creating TDMQ for RocketMQ Resources

Step 2: Using the SDK to Send and Receive Messages (Recommended)

Step 2: Running the TDMQ for RocketMQ Client (Optional)

Step 3: Querying Messages

Step 4: Deleting Resources

User Guide

Usage Process Guide

Configuring Account Permissions

Creating the Cluster

Configuring the Namespace

Configuring the Topic

Configuring the Group

Connecting to the Cluster

Managing Messages

Managing the Cluster

Viewing Monitoring Data and Configuring Alarms

Cross-Cluster Message Replication

Use Cases

Naming Conventions for Common Concepts of TDMQ for RocketMQ

RocketMQ Client Use Cases

RocketMQ Performance Load Testing and Capacity Assessment

Access over HTTP

Client Risk Descriptions and Update Guide

Migration Guide for TencentCloud API Operations Related to RocketMQ 4.x Cluster Roles

Migration Guide

Disruptive Migration

Seamless Migration

Developer Guide

Message Types

Message Filtering

Message Retries

POP Consumption Mode (5.x)

Clustering Consumption and Broadcasting Consumption

Subscription Relationship Consistency

Traffic Throttling

API Reference(5.x)

History

API Category

Making API Requests

Topic APIs

Consumer Group APIs

Message APIs

Role Authentication APIs

Hitless Migration APIs

Cloud Migration APIs

Cluster APIs

Data Types

Error Codes

API Reference(4.x)

SDK Reference

SDK Overview

5.x SDK

4.x SDK

Security and Compliance

Permission Management

CloudAudit

Deletion Protection

FAQs

4.x Instance FAQs

Agreements

TDMQ for RocketMQ Service Level Agreement

Modifying Group Configurations

PDF

フォーカスモード

フォントサイズ

最終更新日: 2026-01-23 17:34:04

After a group is created, you can modify the group configurations based on business requirements, such as adjusting the maximum number of retries and delivery sequentiality to optimize message production and consumption performance.
Constraints and Limitations
After a group is created, its name cannot be modified.
Operation Steps
1. Log in to the TDMQ for RocketMQ console.
2. In the left sidebar, choose Resource > Cluster, select a region, and click the ID of the target cluster to go to the cluster basic information page.
3. On the cluster basic information page, select the Group tab. In the group list, click Edit in the operation column of the target group. In the pop-up window, edit 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
It cannot be modified.
Group Description
It is a string of 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
It cannot be modified.
Protocol Type
It cannot be modified.
Group Description
It is a string of 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 Broadcast
After it is disabled, all consumers declared in the broadcast mode under the group are paused. Re-enabling it can resume consumption.
﻿
4. Click Submit to complete the modification.
﻿
﻿

ヘルプとサポート

この記事はお役に立ちましたか？

営業担当者にお問い合わせいただくかチケットを提出してサポートを求めることができます。

フィードバック

Parameter	Description
Current Cluster	Cluster to which a group belongs, which cannot be modified.
Group Name	It cannot be modified.
Group Description	It is a string of 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	It cannot be modified.
Protocol Type	It cannot be modified.
Group Description	It is a string of 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 Broadcast	After it is disabled, all consumers declared in the broadcast mode under the group are paused. Re-enabling it can resume consumption.

tencent cloud

TDMQ for RocketMQ

Modifying Group Configurations

Constraints and Limitations

Operation Steps

﻿

ヘルプとサポート