You can use Data Transmission Service (DTS) to track data changes in real time. This feature applies to the following scenarios: lightweight cache updates, business decoupling, and synchronization of extract, transform, and load (ETL) operations. This topic describes how to track data changes from an ApsaraDB RDS for MySQL instance.
- DTS does not track data definition language (DDL) operations that are performed by gh-ost or pt-online-schema-change. Therefore, the change tracking client may fail to write the consumed data to the destination tables due to schema conflict.
- If the source database is used in another task, for example, it is used in a running data migration task, DTS may track data changes of other objects. In this case, you must use the change tracking client to filter the tracked data.
- Create a change tracking instance. For more information, see Purchase a change tracking instance.
- Log on to the DTS console.
- In the left-side navigation pane, click Change Tracking.
- At the top of the Change Tracking Tasks page, select the region where the change tracking instance resides.
- Find the change tracking instance and click Configure Channel in the Actions column.
- Configure the source database and network type for the change tracking task.
Section Parameter Description N/A Task Name DTS automatically generates a task name. We recommend that you specify an informative name for easy identification. You do not need to use a unique task name. Source Database Instance Type Select RDS Instance.Note If your source database is a user-created database, you must prepare the environment that is required for the source database. For more information, see Preparation overview. Database Type The value of this parameter is set to MySQL and cannot be changed. Instance Region The source region that you selected on the buy page. You cannot change the value of this parameter. RDS Instance ID Select the ID of the RDS instance from which you want to track data changes.Note A read-only instance or temporary instance cannot be used as the source instance for change tracking. Database Account Enter the database account of the source RDS instance.Note
- The account must have the SELECT permission on the required objects, the REPLICATION CLIENT permission, the REPLICATION SLAVE permission, and the SHOW VIEW permission.
- If the database engine of the source RDS instance is MySQL 5.5 or MySQL 5.6, you do not need to configure the database account or database password.
Database Password Enter the password for the database account of the source RDS instance. Network Type
Select the network type of the change tracking instance.Note
- If your change tracking client is deployed on a local server, you can select Classic or VPC.
- If your change tracking client is deployed on an ECS instance, we recommend that you select the network of the ECS instance. For example, if the ECS instance is deployed in a VPC, select VPC as the network type and specify the VPC and vSwitch.
- If you track data changes over internal networks, the network latency is minimal.
- Click Set Whitelist and Next. The following table describes the details about whitelist settings.
Instance type of the source database Description RDS MySQL The CIDR blocks of DTS servers are automatically added to the whitelist of the source ApsaraDB RDS for MySQL instance. This ensures that DTS servers can connect to the source instance. User-created MySQL database hosted on ECS The CIDR blocks of DTS servers are automatically added to an inbound rule of the ECS instance. This ensures that DTS servers can connect to the source instance.
- User-created MySQL database with a public IP address
- User-created MySQL database connected over Express Connect, VPN Gateway, or Smart Access Gateway
If a whitelist is configured for the user-created database, you must add the CIDR blocks of DTS servers to the whitelist of the database. For more information, see Add the CIDR blocks of DTS servers to the security settings of on-premises databases.
- In the Create Change Tracking Account message, click Next after the account is created.
Note This step is required only when the database engine of the source RDS instance is MySQL 5.5 or MySQL 5.6. In this step, DTS creates a database account for change tracking in the source instance.
- Select the data change types and objects.
Parameter Description Required Data Types
- Data Updates
DTS tracks data updates of the selected objects, including the INSERT, DELETE, and UPDATE operations.
- Schema Updates
DTS tracks the create, delete, and modify operations that are performed on all object schemas of the source instance. You must use the change tracking client to filter the tracked data.
- If you select a database as the object, DTS tracks data changes of all objects, including new objects in the database.
- If you select a table as the object, DTS tracks only data changes of this table. In this case, if you want to track data changes of another table, you must add the table to the required objects. For more information, see Modify the objects for change tracking.
Select objects from the Required Objects section and click the icon to add the objects to the Selected section.Note You can select tables or databases as the objects for change tracking.
- Data Updates
- In the lower-right corner of the page, click Save and Precheck.
- Before you can start the change tracking task, a precheck is performed. You can start the change tracking task only after the task passes the precheck.
- If the task fails to pass the precheck, you can click the icon next to each failed item to view details. You can troubleshoot the issues based on the causes and run a precheck again.
- Close the Precheck dialog box after the following message is displayed: The precheck is passed.
After the change tracking task is configured, DTS performs initial change tracking, which takes about 1 minute. After the initial change tracking is complete, you can create one or more consumer groups to consume the tracked data.