Starting December 1, 2021, new DTS change tracking tasks no longer support classic network connections. Source instances cannot use ApsaraDB or ECS instances in a classic network, and downstream clients must consume tracked data through a virtual private cloud (VPC).
Note This change does not affect DTS change tracking tasks created before December 1, 2021.
Impact and recommendations
-
Scenario 1: You want to create a new DTS change tracking task after December 1, 2021.
Recommendation:- If the source instance is an ApsaraDB instance or an ECS instance, switch it to a VPC or deploy it within a VPC. For example, to learn how to switch the network type of an RDS MySQL instance, see Change the network type.
- Configure a new DTS tracking task and set its network type to VPC. For configuration instructions, see Change tracking solutions.
-
Scenario 2: You have a DTS change tracking task created before December 1, 2021 for a source instance in a classic network, and you need to create a new task to replace it.
Recommendation:- Switch the source instance to a VPC or deploy it within a VPC. For example, to learn how to switch the network type of an RDS MySQL instance, see Change the network type.
- Configure a new DTS tracking task and set its network type to VPC. For configuration instructions, see Change tracking solutions.
- If the timestamp range of the new DTS change tracking task covers the consumer offset of the downstream client for the legacy task, you can switch to the new task. For example, if the consumer offset is 1635847200 (18:00:00 on November 2, 2021 UTC+8) and the new task's timestamp range includes this time, you can continue consuming data from that offset.
For more information about how to consume tracked data, see the following topics: