MySQL patches by Codership

brute force aborts with concurrent DDL

Bug #906603 reported by Seppo Jaakola
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MySQL patches by Codership
Fix Released
Low
Seppo Jaakola
MySQL patches by Codership 5.5.20-23.4
5.5
Fix Released
Low
Seppo Jaakola
MySQL patches by Codership 5.5.20-23.4

Bug Description

Some DDL statements can conflict with access to myisam tables (in mysql database). Currently such conflicts are resolved by aborting other DDL operation, which must not happen in TO isolation model.

To fix:
1. avoid the BF aborting
2. provide TO isolation for mysql database tables

Revision history for this message
Seppo Jaakola (seppo-jaakola) wrote :

fix pushed in wsrep-5.5 for task 1 in: http://bazaar.launchpad.net/~codership/codership-mysql/wsrep-5.5/revision/3653

Revision history for this message
Seppo Jaakola (seppo-jaakola) wrote :

We have server level lock for untargeted DDL.

For a complete fix, the length of isolation period must be extended until close tables phase. However, current fix is enough to sort out the DDL collisions already.

Revision history for this message
Antony Ryabchenko (antony-ryabchenko) wrote :

Thanks a lot for reply, will try the next build and continue testing right now.

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

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.