Jun 7, 2012
tom
No Comments

RDS slave (read replica) not replication

Question

It appears overnight our Master RDS mysql server went offline for 3-4 minutes. When it came back online the replication was broken.

On the slave, issuing SHOW SLAVE STATUS\G;

“Got fatal error 1236 from master when reading data from binary log: ‘Client requested master to start replication from impossible position’”

In AWS monitoring, slave lag shows “-1.0″.

Is there a way to get the slave replication restarted, or should I just create a new slave?

Asked by jaredsten

Answer

There’s really no harm in just spooling up a new slave, so I’d go that route.

Answered by ceejayoz

Check more discussion of this question.

Related posts:

  1. MySQL Master Slave Replication Not Working
  2. MySQL replication: Getting the master in sync with the slave again
  3. Automated failover strategy for master-slave Mysql replication – why would this not work?
  4. Mysql replication, Slow resyncing of slave after an error
  5. MySQL Replication: Move slave to be slave of another slave, without any (or least possible) downtime

Leave a comment