Kafka is a distributed message queue service that features high throughput and high scalability. Kafka is widely used for big data analytics such as log collection, data aggregation, streaming processing, and online and offline analysis. It is important for the big data ecosystem. This topic describes how to synchronize data from a PolarDB cluster compatible with Oracle to a user-created Kafka cluster by using Data Transmission Service (DTS). The data synchronization feature allows you to extend message processing capabilities.
- In this scenario, DTS supports only<dfn class="aliterm" aliterm-def="DTS synchronizes incremental data that is generated in the source database to the destination database." >incremental data synchronization</dfn>.DTS does not support initial schema synchronization and initial full data synchronization.
- A single data synchronization task can synchronize data from only one database. To synchronize data from multiple databases, you must create a data synchronization task for each database.
- To ensure that the delay time of data synchronization is accurate, DTS adds a heartbeat
dts_postgres_heartbeatto the source database. The following figure shows the schema of the heartbeat table.
- Purchase a data synchronization instance. For more information, see Purchase procedure.Note On the buy page, set Source Instance to PolarDB, set Target Instance to Kafka, and then set Synchronization Topology to One-Way Synchronization.
- Log on to the DTS console.
- In the left-side navigation pane, click Data Synchronization.
- At the top of the Synchronization Tasks page, select the region where the destination instance resides.
- Find the data synchronization instance and click Configure Synchronization Channel in the Actions column.
- Configure the source and destination instances.
Section Parameter Description N/A Synchronization 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 Instance Details Instance Type The value of this parameter is set to PolarDB Instance and cannot be changed. Instance Region The region of the source instance. The region is the same as the source region that you selected when you purchased the data synchronization instance. You cannot change the value of this parameter. PolarDB Instance ID Select the ID of the source PolarDB cluster. Database Name Enter the name of the source database. Database Account Enter the privileged account of the source PolarDB cluster. For more information about how to create a privileged database account, see Create database accounts. Database Password Enter the password of the source database account. Destination Instance Details Instance Type Select an instance type based on where the user-created Kafka cluster is deployed. In this example, select User-Created Database with Public IP Address.Note If you select other instance types, you must prepare the environment that is required for the database. For more information, see Preparation overview. Instance Region The region of the destination instance. The region is the same as the destination region that you selected when you purchased the data synchronization instance. You cannot change the value of this parameter. ECS Instance ID Select the ID of the ECS instance on which the Kafka cluster is deployed. Database Type Select Kafka. Port Number Enter the service port number of the Kafka cluster. The default port number is 9092. Database Account Enter the username that is used to log on to the Kafka cluster. If authentication is disabled for the Kafka cluster, you do not need to enter the username. Database Password Enter the password of the cluster account. If authentication is disabled for the Kafka cluster, you do not need to enter the password. Topic Click Get Topic List, and select a topic name from the drop-down list. Kafka Version Select the version of the user-created Kafka cluster. Encryption Select Non-encrypted or SCRAM-SHA-256 based on your business and security requirements.
- In the lower-right corner of the page, click Set Whitelist and Next.Note DTS adds the CIDR blocks of DTS servers to the whitelist of the source PolarDB cluster and the inbound rule of the destination ECS instance. This ensures that DTS servers can connect to the source cluster and the destination instance.
- Select the objects to be synchronized.
Parameter Description Objects Select one or more tables from the Available section and click the icon to move the tables to the Selected section. You can select only tables as the objects to be synchronized.Note DTS maps the table names to the topic name that you select in step 6. If you want to change the topic name, you can move the pointer over the table and click Edit. You must specify a topic that exists in the Kafka cluster. For more information, see Specify the name of an object in the destination instance.
- In the lower-right corner of the page, click Next.
- Configure initial synchronization.
Parameter Description Initial Synchronization Initial Schema Synchronization is selected by default. DTS synchronizes incremental data that is generated in the source database to the destination database. Filter options Ignore DDL in incremental synchronization phase is selected by default. DTS does not synchronize DDL operations that are performed on the source database during incremental data synchronization.
- In the lower-right corner of the page, click Precheck.
- Before you can start the data synchronization task, a precheck is performed. You can start the data synchronization task only after the task passes the precheck.
- If the task fails to pass the precheck, click the icon next to each failed item to view details. Troubleshoot the issues based on the causes and run the precheck again.
- Close the Precheck dialog box after the following message is displayed: The precheck is passed.
- Wait until the initial synchronization is complete and the data synchronization task
is in the Synchronizing state.
On the Synchronization Tasks page, view the status of the data synchronization task.