Bug #48215 IDEMPOTENT breaks on Unique key constraint violation on NDB only.

• Submitted: 21 Oct 22:54
• Reporter: Andrew Hutchings
• Status: Verified
• Category: Server: ClusterRep
• Severity: S2 (Serious)
• Version: mysql-5.1-telco-6.3
• OS: Any
• Tags: 6.3.26
• Triage: Triaged: D2 (Serious) / R6 (Needs Assessment) / E6 (Needs Assessment)

[21 Oct 22:54] Andrew Hutchings

Description:
When hitting a unique key constraint violation an NDB slave will stop whereas other
engines continue in IDEMPOTENT mode.

How to repeat:
master> create table t4 (a int primary key auto_increment, b int, c int, unique (c))
engine=ndb;
master> insert into t4 values(null,1,2),(null,2,3);

mysqldump, insert dump into slave

master> delete from t4 where a=2;
master> show master status;

Use position recorded here to start slave.

master> insert into t4 values (null, 2, 3);

An NDB slave dies here with "Constraint violation e.g. duplicate value in unique index"

Suggested fix:
Either make NDB ignore this or make IDEMPOTENT break here for all engines.