Updated on 2025-09-15 GMT+08:00

Configuring Binlog Pulling

Scenarios

After binlog pulling is enabled, you can pull binlogs through database proxies.

You can choose to pull binlogs from the primary instance or read replicas by toggling on or off the Pull Binlogs from Primary switch.

Constraints

  • To use this function, you need to submit a service ticket to request required permissions.
  • Binlogs can be pulled only when the statuses of your primary DB instance, read replicas, and proxy instance are all Available.
  • The proxy kernel version must be 2.25.06.000 or later.
  • If your proxy does not support binlog pulling, the Pull Binlogs option is not displayed on the console.
  • Whether to pull binlogs from the primary DB instance:
    • Read-only proxies do not support Pull Binlogs from Primary. They pull binlogs from read replicas by default.
    • If you want to pull binlogs from read replicas, set read replica weights for your proxy. If no weight is set, binlogs cannot be pulled from read replicas.

Procedure

  1. Click in the upper left corner and select a region.
  2. Click in the upper left corner of the page and choose Databases > Relational Database Service.
  3. On the Instances page, click the primary instance name to go to the Overview page.
  4. In the navigation pane on the left, choose Database Proxy.
  5. On the displayed page, click next to the Pull Binlogs field.

    Figure 1 Enabling binlog pulling

  6. For read/write proxies, after Pull Binlogs is enabled, click next to the Pull Binlogs from Primary field.

    • If this function is enabled, binlogs are pulled from the primary instance.
    • If this function is disabled, binlogs are pulled from read replicas.
    Figure 2 Enabling Pull Binlogs from Primary