Bug #31527 When mysqld disconnects from cluster no possibility for gap detection is provide
Submitted: 11 Oct 2007 11:48 Modified: 19 Jun 2009 12:33
Reporter: Oli Sennhauser Email Updates:
Status: No Feedback Impact on me:
None 
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:48] Oli Sennhauser 
Description:
When a mysqld writing bin logs is disconncting from the cluster it does not get any statements anymore. This causes gaps in the binary log which makes them unusable for a point in time recovery.
it is wishable to have on the cluster site:
a) an event which shows on which sql-node we have a gap an also possibly from which gcp to which gcp.
b) on the mysqld side a notification, that the binary log is not usable for a PITR.

How to repeat:
just stop and restart mysqld

Suggested fix:
through an event on cluster
notify the mysqld somehow (for example show master status or so)
[19 May 2009 12:33] Jonathan Miller 
Think this has been fixed, do you still see issue?
[19 May 2009 13:13] Oli Sennhauser 
In which release these features where introduced?
[19 Jun 2009 23:00] Bugs System 
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".