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?
There’s really no harm in just spooling up a new slave, so I’d go that route.
- MySQL Master Slave Replication Not Working
- MySQL replication: Getting the master in sync with the slave again
- Automated failover strategy for master-slave Mysql replication – why would this not work?
- Mysql replication, Slow resyncing of slave after an error
- MySQL Replication: Move slave to be slave of another slave, without any (or least possible) downtime
Leave a comment
- Is there a way for administrators to disable users from installing Firefox extensions?
- Is there research material on NTP accuracy available?
- How to create a limited “domain admin” that does not have access to domain controllers?
- Can Windows RDC admin users be immune from being kicked?
- Domain Administrators account policy (After PCI audit)