tencent cloud

TDMQ for Apache Pulsar

Release Notes and Announcements
Release Notes
Cluster Version Updates
Product Announcements
Product Introduction
Introduction and Selection of the TDMQ Product Series
What Is TDMQ for Apache Pulsar
Strengths
Scenarios
How It Works
Product Series
Version Support Instructions for Open-Source Apache Pulsar
Comparison with Open-Source Apache Pulsar
High Availability
Quotas and Limits
Basic Concepts
Billing
Billing Overview
Pricing
Billing Examples
Renewal
Viewing Consumption Details
Overdue Payments
Refund
Getting Started
Getting Started Guide
Preparations
Using the SDK to Send and Receive General Messages
Using the SDK to Send and Receive Advanced Feature Messages
User Guide
Usage Process Guide
Configuring the Account Permission
Creating a Cluster
Configuring the Namespace
Configuring the Topic
Connecting to a Cluster
Managing the Cluster
Querying Messages and Traces
Cross-Region Replication
Viewing Monitoring Data and Configuring Alarm Rules
Use Cases
Client Usage
Abnormal Consumer Isolation
Traffic Throttling Mechanisms
Transaction Reconciliation
Message Idempotence
Message Compression
Migration Guide
Single-Write Multiple-Read Cluster Migration Solutions
Hitless Migration from Virtual Cluster to Pro Cluster
SDK Reference
API Overview
SDK Reference
SDK Overview
Recommended SDK Configuration Parameters
TCP Protocol (Apache Pulsar)
Security and Compliance
Permission Management
Deletion Protection
CloudAudit
FAQs
Monitoring
Clients
Agreements
Service Level Agreement
TDMQ Policy
Contact Us
Glossary

Upgrading the Minor Engine Version

PDF
Focus Mode
Font Size
Last updated: 2025-12-24 15:00:42
TDMQ for Apache Pulsar pro clusters support the upgrade of minor engine versions. You can manually upgrade the minor engine version in the console to gain access to new features, improve performance, and resolve known issues.

Constraints and Limitations

Only pro clusters support the upgrade of the minor version of the cluster engine.
Upgrades from lower to higher versions are supported; downgrades or rollbacks across compatible versions are not allowed.
The system automatically detects and performs minor version upgrades. Specifying a custom target version is not supported.
Compatible version upgrades of the cluster do not incur any additional charges.

Prerequisites

The minor engine version of the cluster can be upgraded only when the Pulsar cluster status is "healthy".

Operation Steps

2. In the left sidebar, choose Cluster, select the target region, and click the ID of the target cluster to go to the Basic Information page.
3. In the Basic Info section, click the Edit button next to the cluster version and set the upgrade time.

Current Version: The current engine version.
Target Version: The target version will be upgraded to the latest version by default. The system automatically detects minor versions. If the Minor Version button cannot be selected, it indicates the cluster is already on the latest minor version. For differences between minor engine versions, see Cluster Version Updates.
Execution Time: You can select Execute or Custom (any time within the next 24 hours). It is recommended to perform the operation during off-peak hours.
4. Click OK to submit the upgrade task and wait for the upgrade process to complete.


Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback