tencent cloud

Data Transfer Service

Release Notes and Announcements
Release Notes
Announcements
Product Introduction
Overview
Data Migration
Data Sync
Data Subscription (Kafka Edition)
Strengths
Supported Regions
Specification Description
Purchase Guide
Billing Overview
Configuration Change Description
Payment Overdue
Refund
Getting Started
Data Migration Guide
Data Sync Guide
Data Subscription Guide (Kafka Edition)
Preparations
Business Evaluation
Network Preparation
Adding DTS IP Addresses to the Allowlist of the Corresponding Databases
DTS Service Permission Preparation
Database and Permission Preparation
Configuring Binlog in Self-Built MySQL
Data Migration
Databases Supported by Data Migration
Cross-Account TencentDB Instance Migration
Migration to MySQL Series
Migrating to PostgreSQL
Migrating to MongoDB
Migrating to SQL Server
Migrating to Tencent Cloud Distributed Cache
Task Management
Data Sync
Databases Supported by Data Sync
Cross-Account TencentDB Instance Sync
Sync to MySQL series
Synchronize to PostgreSQL
Synchronization to MongoDB
Synchronize to Kafka
Task Management
Data Subscription (Kafka Edition)
Databases Supported by Data Subscription
MySQL series Data Subscription
Data Subscription for TDSQL PostgreSQL
MongoDB Data Subscription
Task Management
Consumption Management
Fix for Verification Failure
Check Item Overview
Cutover Description
Monitoring and Alarms
Supported Monitoring Indicators
Supported Events
Configuring Metric Alarms and Event Alarms via the Console
Configuring Indicator Monitoring and Event Alarm by APIs
Ops Management
Configuring Maintenance Time
Task Status Change Description
Practical Tutorial
Synchronizing Local Database to the Cloud
Creating Two-Way Sync Data Structure
Creating Many-to-One Sync Data Structure
Creating Multi-Site Active-Active IDC Architecture
Selecting Data Sync Conflict Resolution Policy
Using CLB as Proxy for Cross-Account Database Migration
Migrating Self-Built Databases to Tencent Cloud Databases via CCN
Best Practices for DTS Performance Tuning
FAQs
Data Migration
Data Sync
FAQs for Data Subscription Kafka Edition
Regular Expressions for Subscription
Error Handling
Common Errors
Failed Connectivity Test
Failed or Alarmed Check Item
Inability to Select Subnet During CCN Access
Slow or Stuck Migration
Data Sync Delay
High Data Subscription Delay
Data Consumption Exception
API Documentation
History
Introduction
API Category
Making API Requests
(NewDTS) Data Migration APIs
Data Sync APIs
Data Consistency Check APIs
(NewDTS) Data Subscription APIs
Data Types
Error Codes
DTS API 2018-03-30
Service Agreement
Service Level Agreements

Use Instructions

PDF
フォーカスモード
フォントサイズ
最終更新日: 2026-02-11 14:48:54

Subscription Operation Instructions

1. The region of the DTS subscription task must be consistent with the region to which the cloud database belongs.
2. After the specified database or collection of the selected subscription object is deleted in the source database, the subscription data (Change Stream) for that database or collection will be invalidated. Even if the database or collection is recreated in the source database, the data subscription cannot be resumed. It is necessary to reset the subscription task and reselect the subscription objects.

Consumption Operation Instructions

1. During data consumption, consumption via public network connection to the Kafka for data subscription is not supported; only access through the Tencent Cloud private network is allowed, and the consumption region must be consistent with the region of the DTS subscription task.
2. To ensure data reentrancy, DTS subscription introduces a Checkpoint mechanism. When messages are written to Kafka Topic, a Checkpoint is generally inserted every 10 seconds to mark the data synchronization checkpoint. After a task interruption and restart, the breakpoint position is identified to enable resumable transfer. Additionally, when the consumer encounters a Checkpoint message, it performs a Kafka consumption offset commit to update the consumption offset in a timely manner.

Built-in Kafka Description

1. The subscribed messages are stored in the DTS built-in Kafka (single-topic). Currently, the default retention period is the most recent 1 day, with a maximum storage capacity of 500G per single-topic. When data storage exceeds 1 day or the data volume surpasses 500G, the built-in Kafka will begin purging the earliest written data. Therefore, users should consume the data promptly to prevent it from being purged before consumption is complete.
2. The built-in Kafka in DTS has a certain upper limit for processing a single message. When a single row of data in the source database exceeds 10MB, this data may be discarded at the consumer side.

Supported SQL Operations for Subscription

Operation Type
Supported SQL Operations
DML
INSERT,UPDATE,DELETE
DDL
INDEX:createIndexes,createIndex,dropIndex,dropIndexes COLLECTION:createCollection,drop,collMod,renameCollection DATABASE:dropDatabase,copyDatabase

ヘルプとサポート

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

フィードバック