BF abort does not work with inserts to table with single unique key
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
MySQL patches by Codership | Status tracked in 5.6 | |||||
5.5 |
Fix Released
|
High
|
Seppo Jaakola | |||
5.6 |
Fix Released
|
High
|
Seppo Jaakola | |||
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC | Status tracked in 5.6 | |||||
5.5 |
Fix Released
|
Undecided
|
Unassigned | |||
5.6 |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
From https:/
Test
create table uniq (u varchar(10), unique key `unique_key`(`u`));
echo "insert into uniq (u) values ('const');" | mysql -h node1 &
echo "insert into uniq (u) values ('const');" | mysql -h node2 &
will make applying to fail on either of the nodes node1 or node2 with duplicate key error:
140328 18:50:51 [ERROR] Slave SQL: Could not execute Write_rows event on table t
est.uniq; Duplicate entry 'const' for key 'unique_key', Error_code: 1062; handle
r error HA_ERR_
or_code: 1062
140328 18:50:51 [Warning] WSREP: RBR event 2 Write_rows apply warning: 121, 3
The reason for this is that locally executing insert does not get BF aborted.
I have seeing no such a problem in 5.5.34-25.9. It's now present in testing. Perhaps, this is а fresh-made bug.