MySQL 5.6 integration issues
Bug #1200647 reported by
Seppo Jaakola
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| MySQL patches by Codership | Status tracked in 5.6 | |||||
| 5.6 |
Fix Released
|
Low
|
Unassigned | |||
| Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC |
Fix Released
|
Undecided
|
Unassigned | |||
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 |
Revision history for this message
| Seppo Jaakola (seppo-jaakola) wrote | #1 |
Revision history for this message
| Seppo Jaakola (seppo-jaakola) wrote | #2 |
Revision history for this message
| Seppo Jaakola (seppo-jaakola) wrote | #3 |
| 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 |
Revision history for this message
| Shahriyar Rzayev (rzayev-sehriyar) wrote | #4 |
To post a comment you must log in.
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: http://