Bug #59889 LOST_EVENTS error 1590 not ignored when --slave-skip-errors used
Submitted: 2 Feb 2011 10:30 Modified: 17 Mar 2011 17:33
Reporter: Geert Vanderkelen Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Cluster: Replication Severity:S3 (Non-critical)
Version:mysql-5.1-telco-7.1 OS:Any
Assigned to: Frazer Clement
Tags: LOST_EVENTS, ndb, replication, slave
Triage: Triaged: D2 (Serious) / R6 (Needs Assessment) / E6 (Needs Assessment)

[2 Feb 2011 10:30] Geert Vanderkelen
Description:
The LOST_EVENTS incident is not ignored when --slave-skip-errors=1590 is used. Using ALL doesn't work either.

How to repeat:
Setup simple replication between MySQL Cluster, but configure slave with --slave-skip-errors=1590.
Stop the Master's mysqld, start it again: Slave will stop not ignoring error 1590.

Suggested fix:
Document that not all errors can be skipped, or make sure 1590 can be skipped.
[17 Mar 2011 17:33] Jon Stephens
Documented bugfix in the NDB-6.3.42, 7.0.23, and 7.1.12 changelogs as follows:

      Error 1590 (ER_SLAVE_INCIDENT) caused the slave to stop even when 
      it was started with --skip-slave-errors=1590.

Closed.