Enabling Binlog Pull for Read Replicas

Scenarios

Binary logs (binlogs) are recorded to track database operations, helping you ensure data consistency and integrity. Pulling binlogs directly from the primary node of a TaurusDB instance can slow down the system response. TaurusDB supports binlog recording and allows third-party tools to pull binlogs. By default, binlog pulling from the primary node is enabled. If you worry about the performance impact, you can pull binlogs from read replicas instead. This helps reduce the load on the primary node and keeps the system running stably.

Supported Versions

You can pull binlogs from read replicas only if the kernel version of your TaurusDB instance is 2.0.54.240600 or later. For details about how to check the kernel version, see How Can I Check the Version of a TaurusDB Instance?

Enabling Binlog Pull for Read Replicas

1. Log in to the TaurusDB console.
2. Click in the upper left corner and select a region and project.
3. On the Instances page, click the target TaurusDB instance name to go to the Basic Information page.
4. In the Configuration area, click under Binlog Pull for Read Replicas.

   

5. In the displayed dialog box, click OK to enable the feature. The DB instance status will change from Binlog pull is being configured for the read replicas to Available. This process takes several seconds.
   Figure 1 Enabling Binlog Pull for Read Replicas