tencent cloud

TDMQ for RocketMQ

DocumentaçãoTDMQ for RocketMQUser GuideManaging the ClusterAdjusting Cluster Specifications

Adjusting Cluster Specifications

Download
Modo Foco
Tamanho da Fonte
Última atualização: 2026-07-14 15:42:52

Scenarios

If the current cluster specifications did not meet your business requirements, you can upgrade your cluster specifications in the console.
Cluster Type
Change Item
Configuration Upgrade
Configuration Downgrade
5.x cluster
Cluster specifications
Supported (basic edition can be upgraded to pro edition).
Not supported (basic edition/pro edition currently cannot be upgraded to platinum edition).
Supported (pro edition can be downgraded to basic edition).
Not supported (platinum edition currently cannot be downgraded to basic edition/pro edition).
TPS Specifications
✓
Supported (basic/pro/platinum editions all support downgrading TPS specifications).
Number of topics
✓
✓
Storage specifications
N/A (pay-as-you-go)
N/A (pay-as-you-go)
4.x exclusive cluster
Node specifications
✓
✓
Number of nodes
✓
×
Single-node storage specifications
✓
×
Number of topics
✓
✓
4.x general cluster
TPS Specifications
✓
×
Storage specifications
✓
×
Number of topics
✓
✓
4.x virtual cluster
/
×
×
Note:
4.x virtual clusters do not support specification upgrades. Because clusters share underlying physical resources, it is recommended that 4.x virtual clusters be migrated to TDMQ for RocketMQ 5.x clusters to ensure high stability and performance. For details, see Migration Guide.

Change Impact/Use Limits

Change Item
Change Impact
Cluster specifications
Upgrading 4.x series clusters to 5.x series clusters is not supported. However, customers can export metadata and switch the access point to manually migrate 4.x series clusters to 5.x series clusters.
4.x clusters do not currently support cross-product-series changes, such as changing from a 4.x exclusive cluster to a 4.x general cluster.
You can freely switch between the Pro, Basic, and Trial editions for 5.x clusters. (Trial Edition has been discontinued.)
TPS Specifications
4.x general clusters do not support TPS specification downgrade.
For other cluster types, you can upgrade or downgrade the TPS specifications within the allowed range of cluster specification changes.
Node specifications
Only 4.x exclusive clusters involve changes to node specifications. Although the number of nodes in exclusive clusters cannot be reduced, you can downgrade node specifications.
Node specification changes theoretically have no impact, but may trigger client disconnections and reconnections. Therefore, certain requests may have a prolonged response time. Monitor your client request status.
Number of topics
Clusters of different specifications have different free tiers of topics. After a specification upgrade/downgrade is completed, the new free tier of topics is enabled.
During cluster specification adjustment, you can also configure the number of topics/groups. However, to ensure that metadata is not lost, the number of configured topics/groups cannot be less than the current number of topics/groups in the cluster.
Availability Zone
During a specification upgrade, you can change the AZ where the cluster resides. Therefore, clusters that previously had a single-AZ risk can have AZs added through the upgrade to ensure cross-AZ disaster recovery.
The change of AZs is affected by the number of cluster nodes. For example, a two-node cluster cannot be deployed across three AZs simultaneously.

Must-Knows

To ensure normal cluster operation, do not perform other operations on the cluster during the cluster specifications change process.
After the cluster specifications change, the fees charged for the cluster will change. The pricing of the new cluster specifications prevails.
Cluster specification changes may trigger client disconnections and reconnections. The client SDK automatically retries, and upper-layer services are theoretically not affected. However, certain requests may have a prolonged response time. Monitor your cluster metrics and alarms promptly.

Prerequisites

You have created a TDMQ for RocketMQ cluster, which is in the Running status.

Operation Steps

Upgrading
Downgrading
There are two entries for upgrading cluster specifications:
Entry 1: Log in to the TDMQ for RocketMQ console, select Cluster in the left sidebar, and click Upgrade in the Operations column of the target cluster.
Entry 2: Log in to the TDMQ for RocketMQ console, and click the ID of the cluster that requires specification adjustment to go to the Basic Information page. Then, click Upgrade in the upper-right corner.
In the pop-up window, select a suitable target cluster specification based on your business requirements. After confirming the cost details, click Confirm the Adjustment and wait for the upgrade to complete.
There are two entries for downgrading cluster specifications:
Entry 1: Log in to the TDMQ for RocketMQ console, select Cluster in the left sidebar, and choose More > Downgrade in the Operations column of the target cluster.
Entry 2: Log in to TDMQ for RocketMQ console, click the ID of the cluster that requires specification adjustment to go to the Basic Information page, and click Downgrade in the upper-right corner.
In the pop-up window, select a suitable target cluster specification based on your business requirements. After confirming the cost details, click Confirm the Adjustment and wait for the downgrade to complete.


Anterior: Viewing and Modifying Basic Cluster InformationPróximo: Configuring Deletion Protection

Ajuda e Suporte

Esta página foi útil?

comentários