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?

ceejayoz · Accepted Answer · 2012-06-06 13:47:07Z

0

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

answered Jun 6, 2012 at 13:47

ceejayoz

33.2k7 gold badges82 silver badges106 bronze badges

I am in this situation and want to replace the malfunctioning replica. The problem is the hostname: can I rename the old replica to something, and then rename the new one to the old one's name, and keep the same hostname as before? Is there anything I need to be aware of? Can something go terribly wrong?
– FrontierPsycho
Jun 17, 2015 at 14:30
@FrontierPsycho You can promote a replica to master, but I don't think you can promote a replica to another replica's spot. We use DNS for this - our master is db.internal.example.com, our read-replica is read-db.internal.example.com, so switching replicas is just a Route53 record change.
– ceejayoz
Jun 17, 2015 at 14:33
That's a better way to do it, although we're using the internal RDS hostname currently, and I'd like to avoid having to change that everywhere it's used. I guess I'll try it and see.
– FrontierPsycho
Jun 17, 2015 at 14:54

Add a comment |

1 Answer 1