ALTER TABLE ... ENGINE=INNODB in one database blocks ALTER TABLE in other databases
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MySQL patches by Codership |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Originally logged here : https:/
Problem Description:
During simultaneous execution of ALTERs on same node, one ALTER TABLE can block the
other ALTER TABLE command even when both are running on two tables from different
databases. This seem to be known limitation.
How to reproduce:
1) Start a mysqld instance with wsrep on.
2) Connection 1:
A long-running ALTER TABLE command on an innodb table say test1.t1
3) Connection 2:
Simultaneously, run another ALTER TABLE on a different innodb table say test2.t2
4) Connection 3:
Monitor the progress from a different connection:
> SHOW PROCESSLIST;
..
| 4 | root | localhost:38774 | test1 | Query | 4 | copy to tmp table | alter table t1 engine=myisam | 26.185 |
| 6 | root | localhost:38784 | test2 | Query | 2 | checking permissions | alter table t2 engine=myisam | 0.000 |
..
tags: | added: maria-5.5-galera |
http:// www.codership. com/wiki/ doku.php? id=faq# qcluster_ stalls_ when_running_ alter_on_ a_table_ which_is_ not_used