Merge lp:~laurynas-biveinis/percona-server/bug1361568 into lp:percona-server/5.6
Status: | Merged |
---|---|
Approved by: | Laurynas Biveinis |
Approved revision: | no longer in the source branch. |
Merged at revision: | 654 |
Proposed branch: | lp:~laurynas-biveinis/percona-server/bug1361568 |
Merge into: | lp:percona-server/5.6 |
Diff against target: |
13 lines (+3/-0) 1 file modified
mysql-test/suite/rpl/t/rpl_err_ignoredtable.test (+3/-0) |
To merge this branch: | bzr merge lp:~laurynas-biveinis/percona-server/bug1361568 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Laurynas Biveinis (community) | Approve | ||
Review via email: mp+232350@code.launchpad.net |
Description of the change
Fix bug 1361568 (Intermittent rpl_err_
trunk).
The bug is in the testcase, the relevant bits are:
connection master1;
select get_lock(
connection master;
...
send update t2 set a = a + 1 + get_lock(
connection master1;
...
kill @id;
drop table t2,t3;
...
connection master;
# The get_lock function causes warning for unsafe statement.
--disable_warnings
--error 0,1317,2013
reap;
KILL and DROP TABLE statements race and may end up in the master1
thread holding the user lock and attempting to drop the tables, while
the master thread hasn't reacted to the kill bit yet, and thus has the
same tables locked and is waiting for the user lock.
Fix with a MariaDB patch that waits for the KILL to complete before
proceeding with the DROP TABLE
(https:/
http://