This topic describes how to create a change tracking task to track data changes from a DRDS instance by using Data Transmission Service (DTS).

Prerequisites

  • A DRDS ​instance is created. For more information, see Create a instance and Create a database.
    Note The storage type of the DRDS instance must be ApsaraDB RDS for MySQL, including custom instance and purchased instance. PolarDB for MySQL cannot be used as the storage type.
  • An ApsaraDB RDS for MySQL instance is created. For more information, see Create an ApsaraDB RDS for MySQL instance.

Limits

Category Description
Limits on the source database
  • The source tables must have PRIMARY KEY or UNIQUE constraints and all fields must be unique. Otherwise, part of the tracked data changes may be duplicate.
  • If you select tables as the objects to track, up to 500 tables can be tracked in a single change tracking task. If you run a task to track more than 500 tables, a request error occurs. In this case, we recommend that you split the tables and configure multiple tasks to track the tables, or configure a change tracking task for the entire database.
  • The following requirements for binary logs of the ApsaraDB RDS for MySQL instances attached to the DRDS instance must be met:
    • The binary logging feature must be enabled. The value of the binlog_row_image parameter must be set to full. Otherwise, error messages are returned during precheck and the change tracking task cannot be started.

    • The binary logs of the source database must be stored for more than 24 hours. Otherwise, DTS may fail to obtain the binary logs and the task may fail. In exceptional circumstances, data inconsistency or loss may occur. Make sure that you set the retention period of binary logs in accordance with the preceding requirements. Otherwise, the Service Level Agreement (SLA) of DTS does not ensure service reliability and performance.
  • A read-only instance or temporary instance cannot be used as the source instance for change tracking.
Other limits
  • When DTS tracks data changes from a DRDS instance, data is distributed across the attached ApsaraDB RDS for MySQL instances. DTS runs a subtask for each ApsaraDB RDS for MySQL instance. The running state of the subtask is displayed in Task Topology.
  • DRDS instances support database and table sharding.If a DDL operation is performed on the source DRDS instance, the DDL operation is performed on all table shards. The progress of each subtask may be inconsistent with that of other subtasks. Therefore, the data tracked by DTS may contain duplicate DDL operations. If you consume these DDL operations multiple times, an exception may occur on the change tracking client. We recommend that you handle the exception as appropriate.
  • Limits on the objects for change tracking:
    • You can track data changes only at the table level.
    • After the change tracking task is configured, the objects for change tracking cannot be reselected. If you want to track data changes of tables that are not included in the selected objects, you must create another change tracking task for the tables.
  • If you perform a primary/secondary switchover on the source instance when the change tracking task is running, the task fails.
  • When the change tracking task is running, do not scale out or scale in the capacity of the source instance, migrate frequently-accessed tables, change shards, or perform DDL operations. Otherwise, the change tracking task fails or data inconsistency occurs.
  • 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.
  • You must make sure that the precision settings for columns of the FLOAT or DOUBLE data type meet your business requirements. DTS uses the ROUND(COLUMN,PRECISION) function to retrieve values from columns of the FLOAT or DOUBLE data type. If you do not specify a precision, DTS sets the precision for the FLOAT data type to 38 digits and the precision for the DOUBLE data type to 308 digits.
  • DTS does not track DDL operations that are performed by using 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 conflicts.

Procedure

  1. Go to the Change Tracking page of the new DTS console.
  2. In the upper-left corner of the page, select the region where the change tracking instance resides.
    Select a region
  3. Click Create Task. On the page that appears, configure the source database and the consumer network type.
    Warning After you select the source instance, we recommend that you read the limits displayed at the top of the page. This helps you create and run the change tracking task.
    Configure the source database
    Section Parameter Description
    N/A Task Name

    DTS automatically generates a task name. We recommend that you specify an informative name to identify the task. You do not need to use a unique task name.

    You can choose whether to use a database connection template.
    • If you use a connection template, DTS automatically applies the parameter settings of the source database.
      Note
      • You can modify the parameter settings of a connection template.
      • To edit the template name, you can click Edit Template Name at the bottom of the Source Database section.
      • The modified connection template will take effect the next time you select the connection template. The database instance that you have configured by using the template is not affected.
    • If you do not use a connection template, you must set parameters for the source database.
    Source Database Select Template
    Database Type Select PolarDB-X 1.0.
    Access Method The value is set to Cloud Instance.
    Instance Region The region where the DRDS instance resides.
    Instance ID The ID of the source DRDS instance.
    Database Account The database account of the source DRDS database. This account must have read permissions on the objects for change tracking.
    Database Password

    Enter the password of the database account.

    Save as Template
    Consumer Network Type
    • Classic
    • VPC
    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 parameters.
    • If you track data changes over internal networks, the network latency is minimal.
    • Classic

      If you select Classic, no other configurations are required. For more information, see Classic network.

    • VPC

      If you select VPC, you must specify the VPC and vSwitch parameters. For more information, see VPCs.

    Notice After a change tracking task is configured, you cannot change the network type. Data changes are tracked and consumed over the specified type of network.
  4. In the lower part of the page, click Test Connectivity and Proceed.
  5. Select objects for the task and configure advanced settings.
    • Basic SettingsBasic Settings
      Parameter Description
      Data Change Types
      • Data Update

        DTS tracks data updates of the selected objects, including the INSERT, DELETE, and UPDATE operations.

      • Schema Update

        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 required data.

      Source Objects Select one or more objects from the Source Objects section and click the Rightwards arrow icon to add the objects to the Selected Objects section.
      Note
      • You can track data changes only at the table level.
      • After the change tracking task is configured, the objects for change tracking cannot be reselected. If you want to track data changes of tables that are not included in the selected objects, you must create another change tracking task for the tables.
    • Advanced SettingsAdvanced Settings
      Parameter Description
      Set Alerts
      Specify whether to set alerts for the change tracking task. If the task fails or the latency exceeds the threshold, the alert contacts will receive notifications.
      • Select No if you do not want to set alerts.
      • Select Yes to set alerts. In this case, you must also set the alert threshold and alert contacts.
      Retry Time for Failed Connections
      Specify the retry time for failed connections. Valid values: 10 to 1440. Unit: minutes. Default value: 120. We recommend that you set the retry time to more than 30 minutes. If DTS reconnects to the source and destination databases within the specified time, DTS resumes the change tracking task. Otherwise, the change tracking task fails.
      Note
      • If multiple DTS instances have the same source or destination database, the lowest value takes effect. For example, the retry time is set to 30 minutes for Instance A and 60 minutes for Instance B, DTS retries failed connections at an interval of 30 minutes.
      • When DTS retries a connection, you are charged for the DTS instance. We recommend that you specify the retry time based on your business needs. You can also release the DTS instance at your earliest opportunity after the source and destination instances are released.
  6. Click Next: Save Task Settings and Precheck in the lower part of the page.
    Note
    • Before you can start the change tracking task, DTS performs a precheck. 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 Info icon icon next to each failed item to view details.
      • You can troubleshoot the issues based on the causes and run a precheck again.
      • If you do not need to troubleshoot the issues, you can ignore failed items and run a precheck again.
  7. Wait until the Success Rate becomes 100%. Then, click Next: Purchase Instance.
  8. On the Purchase Instance page, specify the billing method of the change tracking instance. The following table describes the parameters.
    Parameter Description
    Billing Method
    • Subscription: You can pay for your subscription when you create an instance. We recommend that you select the subscription billing method for long-term use because it is more cost-effective than the pay-as-you-go billing method. You can save more costs with longer subscription periods.
    • Pay-as-you-go: A pay-as-you-go instance is billed on an hourly basis. We recommend that you select the pay-as-you-go billing method for short-term use. If you no longer require your pay-as-you-go instance, you can release it to reduce costs.
    Billing Type of Change Tracking Instance

    If you select the subscription billing method, you can select only USD 120 per month for configuration fee (no data traffic fee) as the billing type of the change tracking instance.

    Subscription Length
    If you select the subscription billing method, set the subscription length and the number of instances that you want to create. The subscription length can be one to nine months or one to three years.
    Note This parameter is available only if you select the subscription billing method.
    Note When a client accesses the change tracking instance over the Internet, DTS charges Internet traffic fee.
  9. Read and select Data Transmission Service (Pay-as-you-go) Service Terms.
  10. Click Buy and Start to start the change tracking task. You can view the progress of the task in the task list.

What to do next

When the change tracking task is running, you can create consumer groups based on the downstream client to consume the tracked data.
  1. For more information about how to create and manage consumer groups, see Create consumer groups.
  2. Use one of the following methods to consume the tracked data: