mirror of
https://github.com/MariaDB/server.git
synced 2025-10-24 08:30:51 +02:00
0a68328673
This is actually an existing problem in the old binlog implementation, and this patch is applicable to old binlog also. The problem is that RESET MASTER can run concurrently with binlog dump threads / connected slaves. This will remove the binlog from under the feet of the reader, which can cause all sorts of strange behaviour. This patch fixes the problem by disallowing to run RESET MASTER when dump threads (or other RESET MASTER or SHOW BINARY LOGS) are running. An error is thrown in this case, user must stop slaves and/or kill dump threads to make the RESET MASTER go through. A slave that connects in the middle of RESET MASTER will wait for it to complete. Fix a lot of test cases to kill any lingering dump threads before doing RESET MASTER, mostly just by sourcing include/kill_binlog_dump_threads.inc. Signed-off-by: Kristian Nielsen <knielsen@knielsen-hq.org>
33 lines
590 B
Text
33 lines
590 B
Text
include/master-slave.inc
|
|
[connection master]
|
|
CREATE TABLE t1 (n INT);
|
|
connection slave;
|
|
include/stop_slave.inc
|
|
connection master;
|
|
include/kill_binlog_dump_threads.inc
|
|
RESET MASTER;
|
|
connection slave;
|
|
include/reset_slave.inc
|
|
connection master;
|
|
SELECT COUNT(*) FROM t1;
|
|
COUNT(*)
|
|
5000
|
|
connection slave;
|
|
LOCK TABLES t1 READ;
|
|
START SLAVE;
|
|
UNLOCK TABLES;
|
|
SELECT COUNT(*) FROM t1;
|
|
COUNT(*)
|
|
5000
|
|
connection master;
|
|
DROP TABLE t1;
|
|
CREATE TABLE t1 (n INT);
|
|
INSERT INTO t1 VALUES(3456);
|
|
connection slave;
|
|
SELECT n FROM t1;
|
|
n
|
|
3456
|
|
connection master;
|
|
DROP TABLE t1;
|
|
connection slave;
|
|
include/rpl_end.inc
|