mirror of
https://github.com/MariaDB/server.git
synced 2026-03-13 03:48:39 +01:00
7081f2a58e
Implement an improved binlog implementation that is integrated into the storage engine. The new implementation is enabled with the --binlog-storage-engine option. Initially the InnoDB storage engine implements the binlog. Integrating the binlog in the storage engine improves performance, since it makes the InnoDB redo log the single source of truth and avoids the need for expensive two-phase commit between binlog and engine. It also makes it possible to disable durability (set --innodb-flush-log-at-trx-commit=0) to further improve performance, while still preserving the ability to recover the binlog and database into a consistent state after a crash. The new binlog implementation also greatly improves the internal design and implementation of the binlog, and enables future enhancements for replication. This is a squash of the original 11.4-based patch series. Signed-off-by: Kristian Nielsen <knielsen@knielsen-hq.org>
77 lines
2.2 KiB
PHP
77 lines
2.2 KiB
PHP
# ==== Purpose ====
|
|
#
|
|
# Terminate all binlog dump threads on a master.
|
|
#
|
|
# This is sometimes useful, as normally such dump threads can hang
|
|
# around for some time before they notice that the slave has disconnected.
|
|
#
|
|
# Note that if there are active slave connections, they might try to
|
|
# reconnect as their dump threads are killed, which may not lead to the
|
|
# desired results.
|
|
#
|
|
#
|
|
# ==== Usage ====
|
|
#
|
|
# [--let $kill_timeout= NUMBER]
|
|
# --source include/stop_slavekill_binlog_dump_threads.inc
|
|
#
|
|
# Parameters:
|
|
# $kill_timeout
|
|
# Maximum number of seconds to wait for dump threads to disappear.
|
|
|
|
|
|
--let $include_filename= kill_binlog_dump_threads.inc
|
|
--source include/begin_include_file.inc
|
|
|
|
--disable_query_log
|
|
|
|
let $wait_counter= 300;
|
|
if ($kill_timeout)
|
|
{
|
|
let $wait_counter= `SELECT $kill_timeout * 10`;
|
|
}
|
|
|
|
let $success= 0;
|
|
while ($wait_counter)
|
|
{
|
|
dec $wait_counter;
|
|
# Tricky here. The binlog dump thread will normally be identified by the
|
|
# command name "Binlog Dump". But if it was killed, but didn't have time
|
|
# to react on the killed yet, it will be 'Killed'. It can also be 'Busy'
|
|
# if the code fails to obtain the LOCK_thd_data mutex.
|
|
let $_tid= `SELECT IF(command='Binlog Dump', id, -1) FROM information_schema.processlist WHERE command IN ('Binlog Dump', 'Killed', 'Busy') LIMIT 1`;
|
|
if ($_tid)
|
|
{
|
|
if ($_tid > 0) {
|
|
--error 0,ER_NO_SUCH_THREAD
|
|
eval KILL CONNECTION $_tid;
|
|
}
|
|
}
|
|
if (!$_tid)
|
|
{
|
|
let $wait_counter= 0;
|
|
let $success= 1;
|
|
}
|
|
if (!$success)
|
|
{
|
|
real_sleep 0.1;
|
|
}
|
|
}
|
|
if (!$success)
|
|
{
|
|
SHOW FULL PROCESSLIST;
|
|
--die Timeout while waiting for binlog dump threads to disappear.
|
|
}
|
|
# This an attempt to get more info about a rare sporadic test failure where
|
|
# RESET MASTER still fails with ER_BINLOG_IN_USE after this has run.
|
|
--let $sanity_check= `SELECT COUNT(*) FROM information_schema.processlist WHERE command = 'Binlog Dump'`
|
|
if ($sanity_check > 0) {
|
|
SHOW FULL PROCESSLIST;
|
|
--echo ERROR: still $sanity_check dump thread(s) found!
|
|
--die ERROR: still $sanity_check dump thread(s) found
|
|
}
|
|
|
|
--enable_query_log
|
|
|
|
--let $include_filename= kill_binlog_dump_threads.inc
|
|
--source include/end_include_file.inc
|