Help Center/ TaurusDB/ User Guide/ Database Proxy (Read/Write Splitting)/ Changing Configurations of a Proxy Instance/ Enabling Binlog Pull for a Proxy Instance
Updated on 2025-09-19 GMT+08:00
View PDF
Share

Enabling Binlog Pull for a Proxy Instance

Scenarios

You can enable binlog pull for a proxy instance and then use the proxy address to pull binlogs from the primary node or read replicas.

Constraints

  • This function is only available when the kernel version of the proxy instance is 2.24.12.000 or later and that of the 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?
  • After this function is enabled for a read-only proxy instance, binlogs can only be pulled from read replicas. So, you must enable binlog pull for read replicas of the TaurusDB instance first.
  • If you want to pull binlogs from a different node (such as from a read replica instead of the primary node), you must disconnect the current connection and reconnect to the desired node.
  • Pulling binlogs from a proxy instance consumes its resources, which increases pressure on the proxy instance and even causes performance issues when binlogs are pulled concurrently.

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and project.
  3. Click in the upper left corner of the page and choose Databases > TaurusDB.
  4. On the Instances page, click the instance name.
  5. In the navigation pane, choose Database Proxy.
  6. Click a proxy instance name to go to the Basic Information page.
  7. In the Proxy Instance Information area, click on the right of Binlog Pull.

    Figure 1 Enabling binlog pull

  8. In the displayed dialog box, click OK.
  1. Log in to the management console.
  2. Click in the upper left corner and select a region and project.
  3. Click in the upper left corner of the page and choose Databases > TaurusDB.
  4. On the Instances page, click the instance name to go to the Basic Information page.
  5. In the Configuration area, click under Binlog Pull for Read Replicas.

  6. In the displayed dialog box, click OK. The DB instance status changes from Binlog pull is being configured for the read replicas to Available. This process takes several seconds.

    Figure 2 Enabling binlog pull for read replicas

  7. In the navigation pane, choose Database Proxy.
  8. Click a proxy instance name to go to the Basic Information page.
  9. In the Proxy Instance Information area, click on the right of Binlog Pull.

    Figure 3 Enabling binlog pull

  10. In the displayed dialog box, click OK. The proxy instance status changes from Changing binlog pull of the proxy instance to Available. This process takes several seconds.
  11. Check whether Binlog Pull for Primary Node is enabled. If it is, click to disable it. Then, binlogs will only be pulled from read replicas.

    Figure 4 Checking whether Binlog Pull for Primary Node is enabled

    Figure 5 Disabling binlog pull for the primary node

Parent Topic: Changing Configurations of a Proxy Instance