summaryrefslogtreecommitdiff
path: root/mysql-test/suite
diff options
context:
space:
mode:
authorHe Zhenxing <zhenxing.he@sun.com>2010-03-30 17:17:19 +0800
committerHe Zhenxing <zhenxing.he@sun.com>2010-03-30 17:17:19 +0800
commit44325dc6b77655dabcdda29886c5598a720cd33f (patch)
treeb5de221a3a3a23956c719144c9bb840806c7023c /mysql-test/suite
parentb2e3fb8a6f0d627591866ff2376ef8a3b61ce739 (diff)
downloadmariadb-git-44325dc6b77655dabcdda29886c5598a720cd33f.tar.gz
Bug#49492 rpl_semi_sync failed on PB2
After stopped slave, it is possible that the Dump thread on master is still running and has locked the semi-sync master plugin, and when uninstalling the semi-sync master plugin, a plugin busy warning could be generated. Fixed by disabling the warnings when uninstalling semi-sync plugin on master.
Diffstat (limited to 'mysql-test/suite')
-rw-r--r--mysql-test/suite/rpl/t/rpl_semi_sync.test4
1 files changed, 4 insertions, 0 deletions
diff --git a/mysql-test/suite/rpl/t/rpl_semi_sync.test b/mysql-test/suite/rpl/t/rpl_semi_sync.test
index b04541aba21..13f5ac70f18 100644
--- a/mysql-test/suite/rpl/t/rpl_semi_sync.test
+++ b/mysql-test/suite/rpl/t/rpl_semi_sync.test
@@ -602,7 +602,11 @@ source include/stop_slave.inc;
UNINSTALL PLUGIN rpl_semi_sync_slave;
connection master;
+# The dump thread may still be running on the master, and so the following
+# UNINSTALL could generate a warning about the plugin is busy.
+disable_warnings;
UNINSTALL PLUGIN rpl_semi_sync_master;
+enable_warnings;
connection slave;
source include/start_slave.inc;