Update | Description | Release Date | Documentation |
Abnormal consumer isolation | When you use the Shared subscription mode, the consumer may experience blocked consumption logic due to machine or system-level issues such as file system or disk I/O bottlenecks. Although the consumption logic is blocked, the network connection between the client and the server remains intact. In this scenario, the server does not consider the consumer offline and continues to push messages. However, since the consumer's consumption logic is blocked, all pushed messages remain unacknowledged, causing a message backlog that cannot be automatically resolved. To mitigate the issue of abnormal message backlogs caused by such scenarios, TDMQ for Apache Pulsar supports the abnormal consumer isolation mechanism. This feature enables proactive detection and isolation of abnormal consumers on the server side. | 2025-05-31 |
Update | Description | Release Date | Documentation |
Support for custom tenant names | You can specify custom tenant names when you create pro clusters. This enables you to migrate data from self-built environments to the cloud. | 2025-04-10 | |
Migration from virtual clusters to pro clusters | The product now features a user-friendly interface to support the migration of virtual clusters to pro clusters. This allows you to benefit from a more feature-rich and technologically stable product offering. | 2025-04-10 | |
Producer and consumer usage percentage | Some namespaces may exceed the predefined producer and consumer quotas. Monitoring alarms are triggered based on the percentage of used quotas rather than fixed thresholds. | 2025-04-10 |
Update | Description | Release Date | Documentation |
Support for automatic topic creation | Pro clusters support automatic topic creation, providing a more convenient way to create metadata. | 2025-01-15 | |
Support for default alarms | Pro clusters support default alarms for cluster-level TPS, bandwidth, and storage utilization to facilitate capacity management. | 2025-01-15 | - |
Update | Description | Release Date | Documentation |
Pro cluster support for creating public network access points | Pro clusters provide a productized approach to creating public network access points. You can monitor public network traffic usage on the cluster monitoring page. | 2024-12-09 | |
Support for a maximum of 128 partitions | Pro clusters of the LARGE specification support a maximum of 128 partitions per topic. | 2024-12-09 |
Update | Description | Release Date | Documentation |
Support for SQL 92 syntax in message filtering | Message filtering supports more flexible SQL 92 syntax, further enriching message filtering capabilities on the server side and simplifying business logic design. | 2024-09-10 |
Update | Description | Release Date | Documentation |
Cross-region replication | Pro clusters support cross-region message replication between clusters. This feature can be used for scenarios such as disaster recovery, data archiving, and cross-region consumption. | 2024-08-27 |
Update | Description | Release Date | Documentation |
Pro clusters - Elastic storage now available | Pro clusters offer a "fixed concurrency scale + elastic storage" model, which maintains technological leadership while reducing storage costs for users. | 2024-03-25 | |
Support for external Prometheus connection | The monitoring data of pro clusters can now be integrated into self-built Prometheus systems. This not only facilitates user observation but also enables Horizontal Pod Autoscaling (HPA) for business workloads based on the monitoring metrics, making online Ops more automated. | 2024-03-25 |
Update | Description | Release Date | Documentation |
Support for cross-region disaster recovery of pro clusters | Message middleware serves as a critical component in the technical architecture of business systems. TDMQ for Apache Pulsar natively supports multi-availability zone disaster recovery capabilities. A cross-region disaster recovery solution has been introduced to address regional disasters. This solution enables customers to rapidly migrate their services and ensure business continuity in such scenarios. | 2024-01-11 | |
Cross-region cold backup solution | TDMQ for Apache Pulsar supports a cross-region cold backup solution, providing the capability for rapid access point switching without requiring business system modifications. | 2024-01-15 | |
Support for custom top-level domain names in the Direct Connect (DC) scenarios | Custom top-level domain names are supported in the DC scenarios. This allows you to access a cluster through your own domain name. | 2024-01-20 | - |
Launch of the Shanghai Autonomous Driving Zone | The Shanghai Autonomous Driving Zone is launched for TDMQ for Apache Pulsar pro clusters. | 2024-01-31 | - |
Update | Description | Release Date | Documentation |
Pro clusters integrate with TF | Pro clusters integrate with TF, supporting creation and deletion. | 2023-12-4 | - |
Update | Description | Release Date | Documentation |
Support for global resource search in the TDMQ for Apache Pulsar console | The TDMQ for Apache Pulsar console supports global resource search. This allows you to quickly locate cluster instances. | 2023-11-27 | - |
Launch of the Jakarta Zone | The Jakarta Zone is launched for TDMQ for Apache Pulsar Pro Edition. | 2023-11-03 | - |
Update | Description | Release Date | Documentation |
Launch of the Silicon Valley Zone | The Silicon Valley Zone is now launched for TDMQ for Apache Pulsar Pro Edition. | 2023-09-05 | - |
Update | Description | Release Date | Documentation |
Topic TTL | Pro clusters support topic-level time-to-live (TTL), which takes precedence over namespace settings, enabling more flexible management of message expiration. | 2023-08-23 |
Update | Description | Release Date | Documentation |
Auto-Create Subscription switch | You can choose whether to enable Auto-Create Subscription in namespace settings. | 2023-06-20 |
Update | Description | Release Date | Documentation |
Batch import of roles | Role Management supports batch import of multiple roles and granting permissions for different namespaces. | 2023-05-29 | - |
Update | Description | Release Date | Documentation |
Support for creating non-persistent messages | You can create non-persistent messages in the console and select the number of partitions for non-persistent messages. | 2022-06-29 | |
Support for setting limits on cluster quotas | To enhance the stability of virtual clusters, limits are imposed on some cluster quotas. Existing clusters are not affected. The range of the TTL for new namespaces is changed to 60 seconds to 1 day. For new virtual clusters, the upper limit of production/consumption TPS per topic partition is reduced from 50,000 to 5,000, and the upper limit of production/consumption bandwidth per topic partition is reduced from 50 MB/s to 5 MB/s. This prevents the mutual impact between users due to excessive traffic. | 2022-06-29 | |
Support for filtering topics by Topic Type and Creation Source in the message topic list | - | 2022-06-29 |
Update | Description | Release Date | Documentation |
Support for viewing the list of topic producers | You can view the list of topic producers, so as to troubleshoot producer-side issues. | 2021-12-23 | |
Display of the number of producers and consumers and alarms for upper limits | The number of producers and consumers and alarms for upper limits is displayed to promptly notify you of any exceptions in a topic. | 2021-12-23 | |
Support for displaying the number of retries and acknowledgment status in message traces | You can view multiple consumer subscription modes, retry behaviors, and acknowledgment status in the message trace for the consumer. | 2021-12-23 | |
Support for pay-as-you-go for TDMQ for Apache Pulsar | TDMQ for Apache Pulsar supports pay-as-you-go and is expected to start billing in January. | 2021-12-23 |
Update | Description | Release Date | Documentation |
Support for cluster-level data statistics | Cluster-level data statistics are supported. This allows you to comprehensively view the usage scale of each cluster, in preparation for the upcoming launch of pay-as-you-go billing. | 2021-10-27 | |
Support for the tag management feature | Resource tags are supported, and tag-based authentication can be managed through Cloud Access Management (CAM), enabling self-developed cloud migration services to implement efficient resource management. | 2021-10-27 | |
New topic-level alarm items | Topic-level alarm items are added, including alarm items for production/consumption rate and traffic, and alarm items for the number of online producers and consumers. | 2021-10-27 | |
Blocking of public network access for clusters | - | 2021-10-27 |
Update | Description | Release Date | Documentation |
Setting of message retention policy for namespaces | Deletion after consumption: Messages are asynchronously cleaned within a certain period after being successfully acknowledged, saving storage space. Persistent retention: Messages are persistently stored based on the maximum retention time and maximum storage space, regardless of whether the messages are consumed. Once the limit is reached, messages are deleted chronologically. | 2021-08-19 | |
Support for forcible deletion of topics and subscriptions | Forcibly deleting topics: A topic with subscriptions can be forcibly deleted, along with its subscriptions. Forcibly deleting subscriptions: A subscription can be forcibly deleted even if it has active consumer connections. | 2021-08-19 |
Update | Description | Release Date | Documentation |
Launch of v2.7.1 clusters | TDMQ for Apache Pulsar supports clusters of version 2.7.1. The cluster version is updated to open-source Apache Pulsar v2.7.1 to support more features and simplify connection. The listenerName dependency is removed for the new cluster version, so you do not need to declare listenerName when connecting to a cluster of version 2.7.1 or later from an open-source Apache Pulsar client. | 2021-05-31 |
Update | Description | Release Date | Documentation |
Launch of the cluster management feature | You can create virtual clusters (which share the underlying resources) and dedicated clusters (which use the underlying resources exclusively) in the console. | 2021-01-14 |
Update | Description | Release Date | Documentation |
Launch of the message query and message trace features | On the Message Query page, you can query the details and trace of a message, including the message content, parameters, duration of each stage, execution result, producer IP, and consumer IP. | 2020-10-30 | |
Open beta of TDMQ for Apache Pulsar | The open beta of TDMQ for Apache Pulsar officially starts. No application is required for the trial use. During the open beta period, certain limits are imposed on the maximum QPS, maximum number of topics, and delayed message concurrency. | 2020-10-12 | - |
Update | Description | Release Date | Documentation |
Support for access to TDMQ for Apache Pulsar from native Pulsar clients | You can access TDMQ for Apache Pulsar from native Pulsar clients. For security reasons, you need to configure the appropriate role permissions in the console and configure the token on the client (which works in the same way as JWT token authentication used in the community). | 2020-09-17 | |
TDMQ for Apache Pulsar upgraded in closed beta to support the native SDK | TDMQ for Apache Pulsar was suspended for upgrade between 09:00 AM and 12:00 PM on September 17, 2020 to support access from native Pulsar clients. | 2020-09-11 | - |
Update | Description | Release Date | Documentation |
TDMQ for Apache Pulsar available in multiple regions | TDMQ for Apache Pulsar was available in the Shanghai region starting from August 9, 2020 and in the Beijing and Chengdu regions starting from August 18, 2020. | 2020-08-18 | - |
Update | Description | Release Date | Documentation |
Launch of TDMQ for Apache Pulsar | TDMQ for Apache Pulsar is a finance-grade distributed message middleware developed based on Pulsar, a top open-source project of Apache. As a message queue that features high consistency, reliability, and concurrency, it has been widely used in the billing scenarios of Tencent, including core transactions, real-time reconciliation, real-time monitoring, and real-time big data analysis. | 2020-06-04 |
Feedback