Replacing your RDS Read Replica

In the event that you need to replace your MySQL read replica for binlog replication, please follow these steps.

If these steps are not followed and we are unable to regain binlog position, all tables will need to be re-dumped which may cause long replication delays in your system.

  1. Start a new instance.

  2. Make sure binlogs are written properly (follow the instructions in Setting up CDC for MySQL on RDS).

  3. Stop replication on the new instance: CALL mysql.rds_stop_replication;

  4. On the old instance, run SHOW MASTER STATUS, and verify Seconds_Behind_Master == 0.

  5. On the Alooma Live view (click Live in the left navigation or nav to look at the _metadata.timestamp field coming from the old instance.

    Wait until it is > current time (this indicates that Alooma has read further in the binlog on the old instance than the new instance's current position).

  6. Delete the input and re-add it, pointing to the new instance.

  7. On the new instance run Call mysql.rds_start_replication.

If you have any questions or concerns about your move to a new read replica, don't hesitate to contact us!

Search results

    No results found