- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Developer Guide
- Operation Guide
- Best Practices
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Cluster APIs
- Namespace APIs
- Topic APIs
- Message APIs
- CMQ Message APIs
- CMQ Management APIs
- UnbindCmqDeadLetter
- RewindCmqQueue
- ModifyCmqTopicAttribute
- ModifyCmqSubscriptionAttribute
- ModifyCmqQueueAttribute
- DescribeCmqTopics
- DescribeCmqTopicDetail
- DescribeCmqSubscriptionDetail
- DescribeCmqQueues
- DescribeCmqQueueDetail
- DescribeCmqDeadLetterSourceQueues
- DeleteCmqTopic
- DeleteCmqSubscribe
- DeleteCmqQueue
- CreateCmqTopic
- CreateCmqSubscribe
- CreateCmqQueue
- Other APIs
- Environment Role APIs
- TDMQ for RabbitMQ APIs
- RocketMQ APIs
- DescribeRocketMQVipInstanceDetail
- DescribeRocketMQMsg
- ModifyRocketMQTopic
- ModifyRocketMQNamespace
- ModifyRocketMQGroup
- ModifyRocketMQCluster
- DescribeRocketMQTopics
- DescribeRocketMQNamespaces
- DescribeRocketMQGroups
- DescribeRocketMQClusters
- DescribeRocketMQCluster
- DeleteRocketMQTopic
- DeleteRocketMQGroup
- DeleteRocketMQCluster
- CreateRocketMQTopic
- CreateRocketMQNamespace
- CreateRocketMQGroup
- CreateRocketMQCluster
- TDMQ for RocketMQ APIs
- Production and Consumption APIs
- Data Types
- Error Codes
- SDK Documentation
- FAQs
- TDMQ Policy
- Service Level Agreement
- General References
- Contact Us
- Glossary
- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Developer Guide
- Operation Guide
- Best Practices
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Cluster APIs
- Namespace APIs
- Topic APIs
- Message APIs
- CMQ Message APIs
- CMQ Management APIs
- UnbindCmqDeadLetter
- RewindCmqQueue
- ModifyCmqTopicAttribute
- ModifyCmqSubscriptionAttribute
- ModifyCmqQueueAttribute
- DescribeCmqTopics
- DescribeCmqTopicDetail
- DescribeCmqSubscriptionDetail
- DescribeCmqQueues
- DescribeCmqQueueDetail
- DescribeCmqDeadLetterSourceQueues
- DeleteCmqTopic
- DeleteCmqSubscribe
- DeleteCmqQueue
- CreateCmqTopic
- CreateCmqSubscribe
- CreateCmqQueue
- Other APIs
- Environment Role APIs
- TDMQ for RabbitMQ APIs
- RocketMQ APIs
- DescribeRocketMQVipInstanceDetail
- DescribeRocketMQMsg
- ModifyRocketMQTopic
- ModifyRocketMQNamespace
- ModifyRocketMQGroup
- ModifyRocketMQCluster
- DescribeRocketMQTopics
- DescribeRocketMQNamespaces
- DescribeRocketMQGroups
- DescribeRocketMQClusters
- DescribeRocketMQCluster
- DeleteRocketMQTopic
- DeleteRocketMQGroup
- DeleteRocketMQCluster
- CreateRocketMQTopic
- CreateRocketMQNamespace
- CreateRocketMQGroup
- CreateRocketMQCluster
- TDMQ for RocketMQ APIs
- Production and Consumption APIs
- Data Types
- Error Codes
- SDK Documentation
- FAQs
- TDMQ Policy
- Service Level Agreement
- General References
- Contact Us
- Glossary
This document describes the updates to TDMQ for Pulsar clusters as well as relevant notes.
Version 2.7.1
Release date: May 17, 2021
Full switch: June 2021
Release notes:
| Update Type | Update | Description | Documentation |
|---|---|---|---|
| Optimization | Unified domain name access | listenerName is removed, so the SDK is more compatible with TCP clients in the community that are not adapted to multiple advertised listeners in Pulsar (including C++, Python, and Node.js). |
|
| Addition | Support for public network access | Public network access is supported, so you can access a TDMQ for Pulsar cluster in Tencent Cloud from a TCP client in your local system or self-built IDC. | Getting Access Address |
| Optimization | Update to the naming conventions for the retry letter and dead letter topics | The naming conventions for the retry letter and dead letter topics are updated to the same as used by the Pulsar community, so that they are more compatible with open-source SDKs (the new naming conventions are not applicable to the original Tencent Cloud SDK) | Message Retry and Dead Letter Mechanisms |
| Optimization | Performance optimization | Clusters on v2.7.1 are optimized at the system kernel level to achieve a 20% higher peak production/consumption performance than clusters on v2.6.x. In addition, they can be scaled imperceptibly according to the actual usage. | - |
| Addition | Support for protocol-compatible plugins (in closed beta test) | You can install plugins compatible with AMQP, RocketMQ, and CMQ in clusters on v2.7.1. Currently, this feature is in beta test. After it is officially launched, you will be able to access TDMQ for Pulsar from popular message queue clients with no modifications required, which will make it easier for you to migrate existing businesses. | - |
Version 2.6.1
Release date: October 12, 2020
Full switch: October 2020
Release notes:
| Update Type | Update | Description | Documentation |
|---|---|---|---|
| Optimization | Stability enhancement | Issues discovered during the beta test are fixed, significantly improving the cluster stability. | - |
| Optimization | Hot/Cold data isolation in ZooKeeper | The ZooKeeper component of the Pulsar kernel adopts the deployment architecture of hot/cold data isolation, where metadata and cluster broker configuration data are deployed separately in two ZooKeeper instances to increase the cluster stability. | - |
| Addition | Support for creation of virtual clusters | You can create virtual clusters in the console for resource isolation. | - |
Upgrade notes:
All newly created clusters will be automatically on the latest version in the current region.
To switch to the new cluster version on your own, follow the steps below:
- Create a cluster (all newly created clusters are on the latest version) and a copy of completely identical metadata (namespaces, role permissions, topics, and subscriptions).
- Replace the original production/consumption access point in the client code with the access address of the new cluster.
- Replace the authentication information (token) in the client code with the token of the new cluster.
- Switch the producer client first (recreate a producer application and deploy it in the production environment).
- Wait for all retained messages in the original cluster to be consumed and then switch the consumer client (recreate a consumer application and deploy it in the production environment).
Yes
No
Was this page helpful?