Bug #31526 Cluster should re-catch up statement propagation to mysqld after disconnect
Submitted: 11 Oct 2007 11:43
Reporter: Oli Sennhauser Email Updates:
Status: Open Impact on me:
Category:MySQL Cluster: Replication Severity:S4 (Feature request)
Version:mysql-5.1 OS:Any
Assigned to: CPU Architecture:Any
Tags: 5.1.x

[11 Oct 2007 11:43] Oli Sennhauser
When a mysqld which is writing bin logs disconnects (for whatever reason) from a cluster it does not get the statements during the disconnect and they are also not delivered later anymore.
This makes the binary log unuesable for a Point In Time Recovery.

How to repeat:
for example stop and start mysqld

Suggested fix:
store all the statement during the disconnect for a certain time.