Binlog Synchronization

The binlog synchronization function can synchronize the incremental data of TiDB to other storages in real time. Supports MySQL, TiDB, Kafka, US3 as target storage.

Enter Management Page

Find the corresponding instance on the product homepage, and click the “Details” button to enter the detailed page.

Enable Binlog

Switch to the “Binlog” panel

The Binlog synchronization service is not enabled by default, click the enable Binlog button to open the enable window

After selecting the appropriate node configuration and the number of nodes, confirm that the fee is correct and click purchase immediately

After successful opening, the status is updated to “Opened”

Full Data Migration, Record CommitTS Data

It is recommended to use UDTS for full migration. After the full migration is completed successfully, UDTS will return CommitTS data.

If it is currently an empty database or no need to migrate the stock data, full migration is not required. You can get the current CommitTS by clicking the “Get CommitTs” button.

Add consumers

Click the “Add Consumer” button to open the add window, and multiple consumers can be added for an instance.

Select MySQL protocol consumer (such as MySQL database, TiDB database or other databases compatible with MySQL protocol) or Kafka, enter the CommitTS data obtained in the previous step and other required information to complete the addition.

View Consumers

In “Step 3: Binlog Consumer”, the currently existing consumers will be listed. You can view the consumer list of corresponding protocols according to different protocols in the upper right corner.

Delete Consumers

When you need to delete a consumer, you can delete it from the consumer list through the “Delete” button.

Close Binlog

When you no longer need the Binlog function, it is recommended to close the Binlog service. This can not only reduce costs but also improve performance.

You must delete all consumers before closing Binlog.

Click the “Close Binlog” button to close the Binlog service.