Data Transmission Service:[Notice] Network type of change tracking tasks created after December 1, 2021 is limited

Scenarios and solutions

• Scenario 1: You need to create a change tracking task after December 1, 2021.

  Solution:

  1. If the source instance is an ApsaraDB RDS instance deployed in the classic network or an ECS instance deployed in the classic network, you must change the network type to VPC. For more information,see Change the network type of an ApsaraDB RDS for MySQL instance.
  2. Configure another change tracking task and set the network type to VPC.

• Scenario 2: You have created a change tracking task before December 1, 2021. The source instance is an ApsaraDB RDS instance deployed in the classic network or an ECS instance deployed in the classic network. After December 1, 2021, you need to create another change tracking task based on the source instance.

  Solution:

  1. Change the network type of the source instance to VPC. For more information, see Change the network type of an ApsaraDB RDS for MySQL instance.
  2. Configure another change tracking task and set the network type to VPC.
  3. When the data range saved by the new change tracking task includes the consumption timestamps recorded in the previous change tracking task, you can resume data consumption by using the new change tracking task. For example, a downstream consumer of the previous change tracking task consumes data at 18:00:00 (UTC+8), November 2, 2021. The consumption timestamp 1635847200 is generated for this point in time. If 2021-11-02 18:00:00 is included in the data range of the new change tracking task, you can resume data consumption from the timestamp by using this task.

     For more information about how to consume the tracked data, see the following topics:

     • Use the SDK demo code to consume tracked data (recommended)
     • Use flink-dts-connector to consume tracked data
     • Use a Kafka client to consume tracked data