This topic describes how to set the latency at which a read-only ApsaraDB RDS for MySQL instance synchronizes data from its primary RDS instance.

Precautions

After you set the data replication latency of a read-only RDS instance, you cannot add the instance to the read/write splitting link. Before you can add the instance to the read/write splitting link, you must set the data replication latency of the instance to 0. For more information, see Enable the read/write splitting function in the shared proxy of an ApsaraDB RDS for MySQL instance.

Invalid read/write splitting

Procedure

  1. Go to the Basic Information page of the read-only RDS instance.
    1. Log on to the ApsaraDB for RDS console. In the left-side navigation pane, click Instances. In the top navigation bar, select the region where your RDS instance resides.
      选择地域
    2. Find the read-only RDS instance and click its ID.
  2. In the left-side navigation pane, click Service Availability.
  3. Click Set Delayed Replication.
  4. In the dialog box that appears, specify the data replication latency and click OK.
    Note The data replication latency is measured in the unit of seconds. The default value is 0. If you set the data replication latency to 0 seconds, the primary RDS instance sends operations logs to the read-only RDS instance after the related operations are complete. After the read-only RDS instance receives the operations logs, it immediately performs the operations that are specified in the operations logs.