MySQL patches by Codership

Deadlock during concurrent dump restore to _different_ databases

Asked by Antony Ryabchenko

Can you suppose something in the case I have deadlock during concurrent dump restore to _different_ databases?
E.g., I have a dump of database db.sql and I restore it from different nodes to different databases. The first started restore always goes well, the same time 2nd and 3rd aborts with the deadlock on the random line of the dump.
I cannot imagine how it can be in the case I restore dumps to the different databases :(

Question information

Language:
English Edit question
Status:
Answered
For:
MySQL patches by Codership Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Seppo Jaakola (seppo-jaakola) said : 		#1

You are probably hitting issue: https://bugs.launchpad.net/codership-mysql/+bug/906603
This issue was observed when concurrently creating/dropping users, but same symptom can happen with database dump loading, in the phase when tables, triggers, procedures etc... are dropped/created.

lp:906603 has been fixed in wsrep-5.5 trunk. You can try the fix by making a source build. Next release build will be prepared for either 1.2 or 2.0 GA release, with ETA in late Jan 2012.

Can you help with this problem?

Provide an answer of your own, or ask Antony Ryabchenko for more information if necessary.

To post a message you must log in.