If you face the above error in any of your RDS replicas, please follow the below steps. When you face this issue you will also see the lag between your master and replica. The status of the “Replication state” will be in “error” state.
- Check the status of the slave by running the below query.
show slave status\G; - Check for the query which is causing this.
- Investigate why this is caused. If that’s not critical run the below query.
CALL mysql.rds_skip_repl_error; - Goto AWS RDS console and check for the “Replication state“. It should be in “Replicating” state but you will see the lag. Late will come down after some time.