MySQL 5.6 integration issues

Bug #1200647 reported by Seppo Jaakola on 2013-07-12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MySQL patches by Codership
Status tracked in 5.6
Percona XtraDB Cluster moved to
Fix Released

Bug Description

Aggregating all initial MySQL 5.6 merge related issues here, until basic cluster functionality has stabilized

Changed in codership-mysql:
status: New → In Progress
importance: Undecided → Low
milestone: none → 5.6.10-23.1
Seppo Jaakola (seppo-jaakola) wrote :

Brute force abort for a transaction which is in lock wait state for some other lock (than the conflicting lock with BF applier), causes assert in debug build. Probably a segfault would happen with optimized build.

Problem is in the way that the victim transaction grants conflicting lock for the BF thread.
Fix is pushed in revision:

Seppo Jaakola (seppo-jaakola) wrote :

DDL processing for a DDL statement, which fails, will cause a segfault. Test case here:

CREATE TABLE t(i int);
CREATE TABLE t(i int);

Segfault will happen during the DROP TABLE processing.

Seppo Jaakola (seppo-jaakola) wrote :

Fix for processing of failing DDL statements pushed in revision:

Changed in percona-xtradb-cluster:
milestone: none → 5.6.14-24.1
Changed in percona-xtradb-cluster:
status: New → Fix Committed
Changed in percona-xtradb-cluster:
status: Fix Committed → Fix Released

Percona now uses JIRA for bug reports so this bug report is migrated to:

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers