Manage a change tracking task

You can use Data Transmission Service (DTS) to retrieve incremental data from data sources in real time. This feature applies to multiple scenarios, such as cache update, business decoupling, asynchronous data processing, real-time synchronization of heterogeneous data, and real-time synchronization of complex extract, transform, and load (ETL) operations. This topic describes how to create, monitor, and manage a change tracking task.

Background information

Overview of change tracking scenarios
This topic describes the databases and data types that are supported by the change tracking feature.
Features
For information about the features of a change tracking task, see Change tracking (new).

Step	Supported version of the change tracking feature	Description
1.Preparation overview	New	Before you use DTS for change tracking, prepare the environments that are required for the source and destination databases.
2.Create a change tracking task	New	Create a change tracking task by completing simple configurations in the DTS console.
3. Manage the change tracking task	New	Create consumer groups After you configure a change tracking task, create one or more consumer groups to consume data. You can create multiple consumer groups for a change tracking task. Consumers in different consumer groups can track data changes from the same data source. Consumer groups allow you to reduce the cost for tracking data changes and improve the efficiency of data consumption. Optional:Manage consumer groups Manage the consumer groups of the change tracking task. For example, you can modify passwords for consumer groups or delete consumer groups. Optional:Modify the objects for change tracking Change the objects whose changes are tracked when the change tracking task is running.
4. Consume tracked data	New	Use one of the following methods to consume the tracked data: Use the SDK demo to consume tracked data Use the SDK demo code to consume the tracked data from a PolarDB-X 1.0 instance Use flink-dts-connector to consume tracked data Use a Kafka client to consume tracked data
5. Stop the change tracking task	New	If you want to stop the change tracking task, release the corresponding instance. Pay-as-you-go: For information about how to release a pay-as-you-go change tracking instance, see Release DTS instances. Subscription: A subscription change tracking instance cannot be manually released. It will be automatically released seven days after the expiration date. Note You can also reset a change tracking task to stop the task. For more information, see Reset a change tracking task.