2017-07-18 14:59:10 +02:00
|
|
|
/* Copyright (c) 2006, 2017, Oracle and/or its affiliates.
|
2017-08-17 11:32:16 +02:00
|
|
|
Copyright (c) 2010, 2017, MariaDB Corporation
|
2006-10-31 12:23:14 +01:00
|
|
|
|
|
|
|
This program is free software; you can redistribute it and/or modify
|
|
|
|
it under the terms of the GNU General Public License as published by
|
2006-12-27 02:23:51 +01:00
|
|
|
the Free Software Foundation; version 2 of the License.
|
2006-10-31 12:23:14 +01:00
|
|
|
|
|
|
|
This program is distributed in the hope that it will be useful,
|
|
|
|
but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
|
|
GNU General Public License for more details.
|
|
|
|
|
|
|
|
You should have received a copy of the GNU General Public License
|
fixes for test failures
and small collateral changes
mysql-test/lib/My/Test.pm:
somehow with "print" we get truncated writes sometimes
mysql-test/suite/perfschema/r/digest_table_full.result:
md5 hashes of statement digests differ, because yacc token codes are different in mariadb
mysql-test/suite/perfschema/r/dml_handler.result:
host table is not ported over yet
mysql-test/suite/perfschema/r/information_schema.result:
host table is not ported over yet
mysql-test/suite/perfschema/r/nesting.result:
this differs, because we don't rewrite general log queries, and multi-statement
packets are logged as a one entry. this result file is identical to what mysql-5.6.5
produces with the --log-raw option.
mysql-test/suite/perfschema/r/relaylog.result:
MariaDB modifies the binlog index file directly, while MySQL 5.6 has a feature "crash-safe binlog index" and modifies a special "crash-safe" shadow copy of the index file and then moves it over. That's why this test shows "NONE" index file writes in MySQL and "MANY" in MariaDB.
mysql-test/suite/perfschema/r/server_init.result:
MariaDB initializes the "manager" resources from the "manager" thread, and starts this thread only when --flush-time is not 0. MySQL 5.6 initializes "manager" resources unconditionally on server startup.
mysql-test/suite/perfschema/r/stage_mdl_global.result:
this differs, because MariaDB disables query cache when query_cache_size=0. MySQL does not
do that, and this causes useless mutex locks and waits.
mysql-test/suite/perfschema/r/statement_digest.result:
md5 hashes of statement digests differ, because yacc token codes are different in mariadb
mysql-test/suite/perfschema/r/statement_digest_consumers.result:
md5 hashes of statement digests differ, because yacc token codes are different in mariadb
mysql-test/suite/perfschema/r/statement_digest_long_query.result:
md5 hashes of statement digests differ, because yacc token codes are different in mariadb
mysql-test/suite/rpl/r/rpl_mixed_drop_create_temp_table.result:
will be updated to match 5.6 when alfranio.correia@oracle.com-20110512172919-c1b5kmum4h52g0ni and anders.song@greatopensource.com-20110105052107-zoab0bsf5a6xxk2y are merged
mysql-test/suite/rpl/r/rpl_non_direct_mixed_mixing_engines.result:
will be updated to match 5.6 when anders.song@greatopensource.com-20110105052107-zoab0bsf5a6xxk2y is merged
2012-09-27 20:09:46 +02:00
|
|
|
along with this program; if not, write to the Free Software Foundation,
|
2019-05-11 18:25:02 +02:00
|
|
|
51 Franklin Street, Fifth Floor, Boston, MA 02110-1335 USA */
|
2006-10-31 12:23:14 +01:00
|
|
|
|
2017-06-18 05:42:16 +02:00
|
|
|
#include "mariadb.h"
|
2010-03-31 16:05:33 +02:00
|
|
|
#include "sql_priv.h"
|
|
|
|
#include "unireg.h" // HAVE_*
|
2007-04-12 08:58:04 +02:00
|
|
|
#include "rpl_mi.h"
|
2006-10-31 12:23:14 +01:00
|
|
|
#include "rpl_rli.h"
|
2010-03-31 16:05:33 +02:00
|
|
|
#include "sql_base.h" // close_thread_tables
|
2006-10-31 12:23:14 +01:00
|
|
|
#include <my_dir.h> // For MY_STAT
|
|
|
|
#include "sql_repl.h" // For check_binlog_magic
|
2010-03-31 16:05:33 +02:00
|
|
|
#include "log_event.h" // Format_description_log_event, Log_event,
|
|
|
|
// FORMAT_DESCRIPTION_LOG_EVENT, ROTATE_EVENT,
|
|
|
|
// PREFIX_SQL_LOAD
|
2007-02-26 17:44:55 +01:00
|
|
|
#include "rpl_utility.h"
|
2009-12-03 19:37:38 +01:00
|
|
|
#include "transaction.h"
|
2010-03-31 16:05:33 +02:00
|
|
|
#include "sql_parse.h" // end_trans, ROLLBACK
|
2016-09-22 08:26:45 +02:00
|
|
|
#include "slave.h"
|
2010-10-28 16:31:21 +02:00
|
|
|
#include <mysql/plugin.h>
|
|
|
|
#include <mysql/service_thd_wait.h>
|
2017-03-06 15:32:54 +01:00
|
|
|
#include "lock.h"
|
|
|
|
#include "sql_table.h"
|
2006-10-31 12:23:14 +01:00
|
|
|
|
2007-08-16 07:37:50 +02:00
|
|
|
static int count_relay_log_space(Relay_log_info* rli);
|
2006-10-31 12:23:14 +01:00
|
|
|
|
2012-11-05 15:01:49 +01:00
|
|
|
/**
|
|
|
|
Current replication state (hash of last GTID executed, per replication
|
|
|
|
domain).
|
|
|
|
*/
|
2015-11-29 16:51:23 +01:00
|
|
|
rpl_slave_state *rpl_global_gtid_slave_state;
|
2014-02-07 19:15:28 +01:00
|
|
|
/* Object used for MASTER_GTID_WAIT(). */
|
|
|
|
gtid_waiting rpl_global_gtid_waiting;
|
2012-11-05 15:01:49 +01:00
|
|
|
|
2016-09-22 08:26:45 +02:00
|
|
|
const char *const Relay_log_info::state_delaying_string = "Waiting until MASTER_DELAY seconds after master executed event";
|
2006-10-31 12:23:14 +01:00
|
|
|
|
BUG#40337 Fsyncing master and relay log to disk after every event is too slow
NOTE: Backporting the patch to next-mr.
The fix proposed in BUG#35542 and BUG#31665 introduces a performance issue
when fsyncing the master.info, relay.info and relay-log.bin* after #th events.
Although such solution has been proposed to reduce the probability of corrupted
files due to a slave-crash, the performance penalty introduced by it has
made the approach impractical for highly intensive workloads.
In a nutshell, the option --syn-relay-log proposed in BUG#35542 and BUG#31665
simultaneously fsyncs master.info, relay-log.info and relay-log.bin* and
this is the main source of performance issues.
This patch introduces new options that give more control to the user on
what should be fsynced and how often:
1) (--sync-master-info, integer) which syncs the master.info after #th event;
2) (--sync-relay-log, integer) which syncs the relay-log.bin* after #th
events.
3) (--sync-relay-log-info, integer) which syncs the relay.info after #th
transactions.
To provide both performance and increased reliability, we recommend the following
setup:
1) --sync-master-info = 0 eventually the operating system will fsync it;
2) --sync-relay-log = 0 eventually the operating system will fsync it;
3) --sync-relay-log-info = 1 fsyncs it after every transaction;
Notice, that the previous setup does not reduce the probability of
corrupted master.info and relay-log.bin*. To overcome the issue, this patch also
introduces a recovery mechanism that right after restart throws away relay-log.bin*
retrieved from a master and updates the master.info based on the relay.info:
4) (--relay-log-recovery, boolean) which enables a recovery mechanism that
throws away relay-log.bin* after a crash.
However, it can only recover the incorrect binlog file and position in master.info,
if other informations (host, port password, etc) are corrupted or incorrect,
then this recovery mechanism will fail to work.
2009-09-29 16:40:52 +02:00
|
|
|
Relay_log_info::Relay_log_info(bool is_slave_recovery)
|
2007-06-09 07:19:37 +02:00
|
|
|
:Slave_reporting_capability("SQL"),
|
2016-09-22 08:26:45 +02:00
|
|
|
replicate_same_server_id(::replicate_same_server_id),
|
2009-09-29 16:27:12 +02:00
|
|
|
info_fd(-1), cur_log_fd(-1), relay_log(&sync_relaylog_period),
|
BUG#40337 Fsyncing master and relay log to disk after every event is too slow
NOTE: Backporting the patch to next-mr.
The fix proposed in BUG#35542 and BUG#31665 introduces a performance issue
when fsyncing the master.info, relay.info and relay-log.bin* after #th events.
Although such solution has been proposed to reduce the probability of corrupted
files due to a slave-crash, the performance penalty introduced by it has
made the approach impractical for highly intensive workloads.
In a nutshell, the option --syn-relay-log proposed in BUG#35542 and BUG#31665
simultaneously fsyncs master.info, relay-log.info and relay-log.bin* and
this is the main source of performance issues.
This patch introduces new options that give more control to the user on
what should be fsynced and how often:
1) (--sync-master-info, integer) which syncs the master.info after #th event;
2) (--sync-relay-log, integer) which syncs the relay-log.bin* after #th
events.
3) (--sync-relay-log-info, integer) which syncs the relay.info after #th
transactions.
To provide both performance and increased reliability, we recommend the following
setup:
1) --sync-master-info = 0 eventually the operating system will fsync it;
2) --sync-relay-log = 0 eventually the operating system will fsync it;
3) --sync-relay-log-info = 1 fsyncs it after every transaction;
Notice, that the previous setup does not reduce the probability of
corrupted master.info and relay-log.bin*. To overcome the issue, this patch also
introduces a recovery mechanism that right after restart throws away relay-log.bin*
retrieved from a master and updates the master.info based on the relay.info:
4) (--relay-log-recovery, boolean) which enables a recovery mechanism that
throws away relay-log.bin* after a crash.
However, it can only recover the incorrect binlog file and position in master.info,
if other informations (host, port password, etc) are corrupted or incorrect,
then this recovery mechanism will fail to work.
2009-09-29 16:40:52 +02:00
|
|
|
sync_counter(0), is_relay_log_recovery(is_slave_recovery),
|
2016-06-10 22:19:59 +02:00
|
|
|
save_temporary_tables(0),
|
|
|
|
mi(0), inuse_relaylog_list(0), last_inuse_relaylog(0),
|
2017-07-24 23:41:54 +02:00
|
|
|
cur_log_old_open_count(0), error_on_rli_init_info(false),
|
|
|
|
group_relay_log_pos(0), event_relay_log_pos(0),
|
2008-02-18 12:35:44 +01:00
|
|
|
group_master_log_pos(0), log_space_total(0), ignore_log_space_limit(0),
|
2014-01-08 11:00:44 +01:00
|
|
|
last_master_timestamp(0), sql_thread_caught_up(true), slave_skip_counter(0),
|
Fixes for parallel slave:
- Made slaves temporary table multi-thread slave safe by adding mutex around save_temporary_table usage.
- rli->save_temporary_tables is the active list of all used temporary tables
- This is copied to THD->temporary_tables when temporary tables are opened and updated when temporary tables are closed
- Added THD->lock_temporary_tables() and THD->unlock_temporary_tables() to simplify this.
- Relay_log_info->sql_thd renamed to Relay_log_info->sql_driver_thd to avoid wrong usage for merged code.
- Added is_part_of_group() to mark functions that are part of the next function. This replaces setting IN_STMT when events are executed.
- Added is_begin(), is_commit() and is_rollback() functions to Query_log_event to simplify code.
- If slave_skip_counter is set run things in single threaded mode. This simplifies code for skipping events.
- Updating state of relay log (IN_STMT and IN_TRANSACTION) is moved to one single function: update_state_of_relay_log()
We can't use OPTION_BEGIN to check for the state anymore as the sql_driver and sql execution threads may be different.
Clear IN_STMT and IN_TRANSACTION in init_relay_log_pos() and Relay_log_info::cleanup_context() to ensure the flags doesn't survive slave restarts
is_in_group() is now independent of state of executed transaction.
- Reset thd->transaction.all.modified_non_trans_table() if we did set it for single table row events.
This was mainly for keeping the flag as documented.
- Changed slave_open_temp_tables to uint32 to be able to use atomic operators on it.
- Relay_log_info::sleep_lock -> rpl_group_info::sleep_lock
- Relay_log_info::sleep_cond -> rpl_group_info::sleep_cond
- Changed some functions to take rpl_group_info instead of Relay_log_info to make them multi-slave safe and to simplify usage
- do_shall_skip()
- continue_group()
- sql_slave_killed()
- next_event()
- Simplifed arguments to io_salve_killed(), check_io_slave_killed() and sql_slave_killed(); No reason to supply THD as this is part of the given structure.
- set_thd_in_use_temporary_tables() removed as in_use is set on usage
- Added information to thd_proc_info() which thread is waiting for slave mutex to exit.
- In open_table() reuse code from find_temporary_table()
Other things:
- More DBUG statements
- Fixed the rpl_incident.test can be run with --debug
- More comments
- Disabled not used function rpl_connect_master()
mysql-test/suite/perfschema/r/all_instances.result:
Moved sleep_lock and sleep_cond to rpl_group_info
mysql-test/suite/rpl/r/rpl_incident.result:
Updated result
mysql-test/suite/rpl/t/rpl_incident-master.opt:
Not needed anymore
mysql-test/suite/rpl/t/rpl_incident.test:
Fixed that test can be run with --debug
sql/handler.cc:
More DBUG_PRINT
sql/log.cc:
More comments
sql/log_event.cc:
Added DBUG statements
do_shall_skip(), continue_group() now takes rpl_group_info param
Use is_begin(), is_commit() and is_rollback() functions instead of inspecting query string
We don't have set slaves temporary tables 'in_use' as this is now done when tables are opened.
Removed IN_STMT flag setting. This is now done in update_state_of_relay_log()
Use IN_TRANSACTION flag to test state of relay log.
In rows_event_stmt_cleanup() reset thd->transaction.all.modified_non_trans_table if we had set this before.
sql/log_event.h:
do_shall_skip(), continue_group() now takes rpl_group_info param
Added is_part_of_group() to mark events that are part of the next event. This replaces setting IN_STMT when events are executed.
Added is_begin(), is_commit() and is_rollback() functions to Query_log_event to simplify code.
sql/log_event_old.cc:
Removed IN_STMT flag setting. This is now done in update_state_of_relay_log()
do_shall_skip(), continue_group() now takes rpl_group_info param
sql/log_event_old.h:
Added is_part_of_group() to mark events that are part of the next event.
do_shall_skip(), continue_group() now takes rpl_group_info param
sql/mysqld.cc:
Changed slave_open_temp_tables to uint32 to be able to use atomic operators on it.
Relay_log_info::sleep_lock -> Rpl_group_info::sleep_lock
Relay_log_info::sleep_cond -> Rpl_group_info::sleep_cond
sql/mysqld.h:
Updated types and names
sql/rpl_gtid.cc:
More DBUG
sql/rpl_parallel.cc:
Updated TODO section
Set thd for event that is execution
Use new is_begin(), is_commit() and is_rollback() functions.
More comments
sql/rpl_rli.cc:
sql_thd -> sql_driver_thd
Relay_log_info::sleep_lock -> rpl_group_info::sleep_lock
Relay_log_info::sleep_cond -> rpl_group_info::sleep_cond
Clear IN_STMT and IN_TRANSACTION in init_relay_log_pos() and Relay_log_info::cleanup_context() to ensure the flags doesn't survive slave restarts.
Reset table->in_use for temporary tables as the table may have been used by another THD.
Use IN_TRANSACTION instead of OPTION_BEGIN to check state of relay log.
Removed IN_STMT flag setting. This is now done in update_state_of_relay_log()
sql/rpl_rli.h:
Changed relay log state flags to bit masks instead of bit positions (most other code we have uses bit masks)
Added IN_TRANSACTION to mark if we are in a BEGIN ... COMMIT section.
save_temporary_tables is now thread safe
Relay_log_info::sleep_lock -> rpl_group_info::sleep_lock
Relay_log_info::sleep_cond -> rpl_group_info::sleep_cond
Relay_log_info->sql_thd renamed to Relay_log_info->sql_driver_thd to avoid wrong usage for merged code
is_in_group() is now independent of state of executed transaction.
sql/slave.cc:
Simplifed arguments to io_salve_killed(), sql_slave_killed() and check_io_slave_killed(); No reason to supply THD as this is part of the given structure.
set_thd_in_use_temporary_tables() removed as in_use is set on usage in sql_base.cc
sql_thd -> sql_driver_thd
More DBUG
Added update_state_of_relay_log() which will calculate the IN_STMT and IN_TRANSACTION state of the relay log after the current element is executed.
If slave_skip_counter is set run things in single threaded mode.
Simplifed arguments to io_salve_killed(), check_io_slave_killed() and sql_slave_killed(); No reason to supply THD as this is part of the given structure.
Added information to thd_proc_info() which thread is waiting for slave mutex to exit.
Disabled not used function rpl_connect_master()
Updated argument to next_event()
sql/sql_base.cc:
Added mutex around usage of slave's temporary tables. The active list is always kept up to date in sql->rgi_slave->save_temporary_tables.
Clear thd->temporary_tables after query (safety)
More DBUG
When using temporary table, set table->in_use to current thd as the THD may be different for slave threads.
Some code is ifdef:ed with REMOVE_AFTER_MERGE_WITH_10 as the given code in 10.0 is not yet in this tree.
In open_table() reuse code from find_temporary_table()
sql/sql_binlog.cc:
rli->sql_thd -> rli->sql_driver_thd
Remove duplicate setting of rgi->rli
sql/sql_class.cc:
Added helper functions rgi_lock_temporary_tables() and rgi_unlock_temporary_tables()
Would have been nicer to have these inline, but there was no easy way to do that
sql/sql_class.h:
Added functions to protect slaves temporary tables
sql/sql_parse.cc:
Added DBUG_PRINT
sql/transaction.cc:
Added comment
2013-10-13 23:24:05 +02:00
|
|
|
abort_pos_wait(0), slave_run_id(0), sql_driver_thd(),
|
MDEV-6589: Incorrect relay log start position when restarting SQL thread after error in parallel replication
The problem occurs in parallel replication in GTID mode, when we are using
multiple replication domains. In this case, if the SQL thread stops, the
slave GTID position may refer to a different point in the relay log for each
domain.
The bug was that when the SQL thread was stopped and restarted (but the IO
thread was kept running), the SQL thread would resume applying the relay log
from the point of the most advanced replication domain, silently skipping all
earlier events within other domains. This caused replication corruption.
This patch solves the problem by storing, when the SQL thread stops with
multiple parallel replication domains active, the current GTID
position. Additionally, the current position in the relay logs is moved back
to a point known to be earlier than the current position of any replication
domain. Then when the SQL thread restarts from the earlier position, GTIDs
encountered are compared against the stored GTID position. Any GTID that was
already applied before the stop is skipped to avoid duplicate apply.
This patch should have no effect if multi-domain GTID parallel replication is
not used. Similarly, if both SQL and IO thread are stopped and restarted, the
patch has no effect, as in this case the existing relay logs are removed and
re-fetched from the master at the current global @@gtid_slave_pos.
2015-02-18 12:22:50 +01:00
|
|
|
gtid_skip_flag(GTID_SKIP_NOT), inited(0), abort_slave(0), stop_for_until(0),
|
2016-01-03 12:20:07 +01:00
|
|
|
slave_running(MYSQL_SLAVE_NOT_RUN), until_condition(UNTIL_NONE),
|
2012-10-03 00:44:54 +02:00
|
|
|
until_log_pos(0), retried_trans(0), executed_entries(0),
|
2016-09-22 08:26:45 +02:00
|
|
|
sql_delay(0), sql_delay_end(0),
|
2013-10-14 23:17:16 +02:00
|
|
|
m_flags(0)
|
2006-10-31 12:23:14 +01:00
|
|
|
{
|
2007-08-16 07:37:50 +02:00
|
|
|
DBUG_ENTER("Relay_log_info::Relay_log_info");
|
2006-10-31 12:23:14 +01:00
|
|
|
|
2012-12-14 15:38:07 +01:00
|
|
|
relay_log.is_relay_log= TRUE;
|
2016-04-28 16:15:38 +02:00
|
|
|
relay_log_state.init();
|
2011-03-01 17:39:28 +01:00
|
|
|
#ifdef HAVE_PSI_INTERFACE
|
|
|
|
relay_log.set_psi_keys(key_RELAYLOG_LOCK_index,
|
2017-10-26 16:20:20 +02:00
|
|
|
key_RELAYLOG_COND_relay_log_updated,
|
|
|
|
key_RELAYLOG_COND_bin_log_updated,
|
2011-03-01 17:39:28 +01:00
|
|
|
key_file_relaylog,
|
2011-10-25 12:53:40 +02:00
|
|
|
key_file_relaylog_index,
|
2017-11-22 16:10:34 +01:00
|
|
|
key_RELAYLOG_COND_queue_busy,
|
|
|
|
key_LOCK_relaylog_end_pos);
|
2011-03-01 17:39:28 +01:00
|
|
|
#endif
|
|
|
|
|
2006-10-31 12:23:14 +01:00
|
|
|
group_relay_log_name[0]= event_relay_log_name[0]=
|
|
|
|
group_master_log_name[0]= 0;
|
2007-06-09 07:19:37 +02:00
|
|
|
until_log_name[0]= ign_master_log_name_end[0]= 0;
|
2012-10-01 01:30:44 +02:00
|
|
|
max_relay_log_size= global_system_variables.max_relay_log_size;
|
2006-10-31 12:23:14 +01:00
|
|
|
bzero((char*) &info_file, sizeof(info_file));
|
|
|
|
bzero((char*) &cache_buf, sizeof(cache_buf));
|
2010-01-07 06:42:07 +01:00
|
|
|
mysql_mutex_init(key_relay_log_info_run_lock, &run_lock, MY_MUTEX_INIT_FAST);
|
|
|
|
mysql_mutex_init(key_relay_log_info_data_lock,
|
|
|
|
&data_lock, MY_MUTEX_INIT_FAST);
|
|
|
|
mysql_mutex_init(key_relay_log_info_log_space_lock,
|
|
|
|
&log_space_lock, MY_MUTEX_INIT_FAST);
|
|
|
|
mysql_cond_init(key_relay_log_info_data_cond, &data_cond, NULL);
|
|
|
|
mysql_cond_init(key_relay_log_info_start_cond, &start_cond, NULL);
|
|
|
|
mysql_cond_init(key_relay_log_info_stop_cond, &stop_cond, NULL);
|
|
|
|
mysql_cond_init(key_relay_log_info_log_space_cond, &log_space_cond, NULL);
|
2006-10-31 12:23:14 +01:00
|
|
|
relay_log.init_pthread_objects();
|
|
|
|
DBUG_VOID_RETURN;
|
|
|
|
}
|
|
|
|
|
|
|
|
|
2007-08-16 07:37:50 +02:00
|
|
|
Relay_log_info::~Relay_log_info()
|
2006-10-31 12:23:14 +01:00
|
|
|
{
|
2007-08-16 07:37:50 +02:00
|
|
|
DBUG_ENTER("Relay_log_info::~Relay_log_info");
|
2006-10-31 12:23:14 +01:00
|
|
|
|
MDEV-6589: Incorrect relay log start position when restarting SQL thread after error in parallel replication
The problem occurs in parallel replication in GTID mode, when we are using
multiple replication domains. In this case, if the SQL thread stops, the
slave GTID position may refer to a different point in the relay log for each
domain.
The bug was that when the SQL thread was stopped and restarted (but the IO
thread was kept running), the SQL thread would resume applying the relay log
from the point of the most advanced replication domain, silently skipping all
earlier events within other domains. This caused replication corruption.
This patch solves the problem by storing, when the SQL thread stops with
multiple parallel replication domains active, the current GTID
position. Additionally, the current position in the relay logs is moved back
to a point known to be earlier than the current position of any replication
domain. Then when the SQL thread restarts from the earlier position, GTIDs
encountered are compared against the stored GTID position. Any GTID that was
already applied before the stop is skipped to avoid duplicate apply.
This patch should have no effect if multi-domain GTID parallel replication is
not used. Similarly, if both SQL and IO thread are stopped and restarted, the
patch has no effect, as in this case the existing relay logs are removed and
re-fetched from the master at the current global @@gtid_slave_pos.
2015-02-18 12:22:50 +01:00
|
|
|
reset_inuse_relaylog();
|
2010-01-07 06:42:07 +01:00
|
|
|
mysql_mutex_destroy(&run_lock);
|
|
|
|
mysql_mutex_destroy(&data_lock);
|
|
|
|
mysql_mutex_destroy(&log_space_lock);
|
|
|
|
mysql_cond_destroy(&data_cond);
|
|
|
|
mysql_cond_destroy(&start_cond);
|
|
|
|
mysql_cond_destroy(&stop_cond);
|
|
|
|
mysql_cond_destroy(&log_space_cond);
|
2006-10-31 12:23:14 +01:00
|
|
|
relay_log.cleanup();
|
|
|
|
DBUG_VOID_RETURN;
|
|
|
|
}
|
|
|
|
|
|
|
|
|
2016-09-22 08:26:45 +02:00
|
|
|
/**
|
|
|
|
Read the relay_log.info file.
|
|
|
|
|
|
|
|
@param info_fname The name of the file to read from.
|
|
|
|
@retval 0 success
|
|
|
|
@retval 1 failure
|
|
|
|
*/
|
|
|
|
int Relay_log_info::init(const char* info_fname)
|
2006-10-31 12:23:14 +01:00
|
|
|
{
|
|
|
|
char fname[FN_REFLEN+128];
|
|
|
|
const char* msg = 0;
|
|
|
|
int error = 0;
|
2017-06-04 10:47:30 +02:00
|
|
|
mysql_mutex_t *log_lock;
|
2016-09-22 13:36:45 +02:00
|
|
|
DBUG_ENTER("Relay_log_info::init");
|
2006-10-31 12:23:14 +01:00
|
|
|
|
2016-09-22 08:26:45 +02:00
|
|
|
if (inited) // Set if this function called
|
2006-10-31 12:23:14 +01:00
|
|
|
DBUG_RETURN(0);
|
2017-06-04 10:47:30 +02:00
|
|
|
|
2017-07-05 19:08:55 +02:00
|
|
|
log_lock= relay_log.get_log_lock();
|
2006-10-31 12:23:14 +01:00
|
|
|
fn_format(fname, info_fname, mysql_data_home, "", 4+32);
|
2016-09-22 08:26:45 +02:00
|
|
|
mysql_mutex_lock(&data_lock);
|
|
|
|
cur_log_fd = -1;
|
|
|
|
slave_skip_counter=0;
|
|
|
|
abort_pos_wait=0;
|
|
|
|
log_space_limit= relay_log_space_limit;
|
|
|
|
log_space_total= 0;
|
2006-10-31 12:23:14 +01:00
|
|
|
|
2018-04-04 11:16:12 +02:00
|
|
|
if (unlikely(error_on_rli_init_info))
|
2017-02-28 05:30:51 +01:00
|
|
|
goto err;
|
2006-10-31 12:23:14 +01:00
|
|
|
|
2009-04-19 03:21:33 +02:00
|
|
|
char pattern[FN_REFLEN];
|
2009-11-28 05:43:16 +01:00
|
|
|
(void) my_realpath(pattern, slave_load_tmpdir, 0);
|
|
|
|
if (fn_format(pattern, PREFIX_SQL_LOAD, pattern, "",
|
2009-04-19 03:21:33 +02:00
|
|
|
MY_SAFE_PATH | MY_RETURN_REAL_PATH) == NullS)
|
|
|
|
{
|
2016-09-22 08:26:45 +02:00
|
|
|
mysql_mutex_unlock(&data_lock);
|
2009-04-19 03:21:33 +02:00
|
|
|
sql_print_error("Unable to use slave's temporary directory %s",
|
|
|
|
slave_load_tmpdir);
|
|
|
|
DBUG_RETURN(1);
|
|
|
|
}
|
2016-09-22 08:26:45 +02:00
|
|
|
unpack_filename(slave_patternload_file, pattern);
|
|
|
|
slave_patternload_file_size= strlen(slave_patternload_file);
|
2009-02-21 10:36:07 +01:00
|
|
|
|
2006-10-31 12:23:14 +01:00
|
|
|
/*
|
|
|
|
The relay log will now be opened, as a SEQ_READ_APPEND IO_CACHE.
|
|
|
|
Note that the I/O thread flushes it to disk after writing every
|
2010-02-03 17:56:17 +01:00
|
|
|
event, in flush_master_info(mi, 1, ?).
|
2006-10-31 12:23:14 +01:00
|
|
|
*/
|
|
|
|
|
|
|
|
{
|
2009-11-05 07:07:31 +01:00
|
|
|
/* Reports an error and returns, if the --relay-log's path
|
|
|
|
is a directory.*/
|
|
|
|
if (opt_relay_logname &&
|
|
|
|
opt_relay_logname[strlen(opt_relay_logname) - 1] == FN_LIBCHAR)
|
|
|
|
{
|
2016-09-22 08:26:45 +02:00
|
|
|
mysql_mutex_unlock(&data_lock);
|
2009-11-05 07:07:31 +01:00
|
|
|
sql_print_error("Path '%s' is a directory name, please specify \
|
|
|
|
a file name for --relay-log option", opt_relay_logname);
|
|
|
|
DBUG_RETURN(1);
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Reports an error and returns, if the --relay-log-index's path
|
|
|
|
is a directory.*/
|
|
|
|
if (opt_relaylog_index_name &&
|
|
|
|
opt_relaylog_index_name[strlen(opt_relaylog_index_name) - 1]
|
|
|
|
== FN_LIBCHAR)
|
|
|
|
{
|
2016-09-22 08:26:45 +02:00
|
|
|
mysql_mutex_unlock(&data_lock);
|
2009-11-05 07:07:31 +01:00
|
|
|
sql_print_error("Path '%s' is a directory name, please specify \
|
|
|
|
a file name for --relay-log-index option", opt_relaylog_index_name);
|
|
|
|
DBUG_RETURN(1);
|
|
|
|
}
|
|
|
|
|
2006-10-31 12:23:14 +01:00
|
|
|
char buf[FN_REFLEN];
|
|
|
|
const char *ln;
|
|
|
|
static bool name_warning_sent= 0;
|
2016-09-22 08:26:45 +02:00
|
|
|
ln= relay_log.generate_name(opt_relay_logname, "-relay-bin",
|
2006-10-31 12:23:14 +01:00
|
|
|
1, buf);
|
|
|
|
/* We send the warning only at startup, not after every RESET SLAVE */
|
2013-01-11 01:03:43 +01:00
|
|
|
if (!opt_relay_logname && !opt_relaylog_index_name && !name_warning_sent &&
|
|
|
|
!opt_bootstrap)
|
2006-10-31 12:23:14 +01:00
|
|
|
{
|
|
|
|
/*
|
|
|
|
User didn't give us info to name the relay log index file.
|
|
|
|
Picking `hostname`-relay-bin.index like we do, causes replication to
|
|
|
|
fail if this slave's hostname is changed later. So, we would like to
|
|
|
|
instead require a name. But as we don't want to break many existing
|
|
|
|
setups, we only give warning, not error.
|
|
|
|
*/
|
|
|
|
sql_print_warning("Neither --relay-log nor --relay-log-index were used;"
|
|
|
|
" so replication "
|
|
|
|
"may break when this MySQL server acts as a "
|
|
|
|
"slave and has his hostname changed!! Please "
|
2011-03-28 02:02:24 +02:00
|
|
|
"use '--log-basename=#' or '--relay-log=%s' to avoid "
|
2011-03-23 16:59:41 +01:00
|
|
|
"this problem.", ln);
|
2006-10-31 12:23:14 +01:00
|
|
|
name_warning_sent= 1;
|
|
|
|
}
|
2011-05-03 14:01:11 +02:00
|
|
|
|
2012-09-28 01:06:56 +02:00
|
|
|
/* For multimaster, add connection name to relay log filenames */
|
|
|
|
char buf_relay_logname[FN_REFLEN], buf_relaylog_index_name_buff[FN_REFLEN];
|
|
|
|
char *buf_relaylog_index_name= opt_relaylog_index_name;
|
|
|
|
|
2013-05-03 00:50:42 +02:00
|
|
|
create_logfile_name_with_suffix(buf_relay_logname,
|
|
|
|
sizeof(buf_relay_logname),
|
|
|
|
ln, 1, &mi->cmp_connection_name);
|
2012-09-28 01:06:56 +02:00
|
|
|
ln= buf_relay_logname;
|
|
|
|
|
|
|
|
if (opt_relaylog_index_name)
|
|
|
|
{
|
|
|
|
buf_relaylog_index_name= buf_relaylog_index_name_buff;
|
2012-10-03 00:44:54 +02:00
|
|
|
create_logfile_name_with_suffix(buf_relaylog_index_name_buff,
|
2013-05-03 00:50:42 +02:00
|
|
|
sizeof(buf_relaylog_index_name_buff),
|
|
|
|
opt_relaylog_index_name, 0,
|
|
|
|
&mi->cmp_connection_name);
|
2012-09-28 01:06:56 +02:00
|
|
|
}
|
|
|
|
|
2006-10-31 12:23:14 +01:00
|
|
|
/*
|
|
|
|
note, that if open() fails, we'll still have index file open
|
|
|
|
but a destructor will take care of that
|
|
|
|
*/
|
2017-02-10 19:30:37 +01:00
|
|
|
mysql_mutex_lock(log_lock);
|
2016-09-22 08:26:45 +02:00
|
|
|
if (relay_log.open_index_file(buf_relaylog_index_name, ln, TRUE) ||
|
|
|
|
relay_log.open(ln, LOG_BIN, 0, 0, SEQ_READ_APPEND,
|
2017-09-28 12:38:02 +02:00
|
|
|
(ulong)max_relay_log_size, 1, TRUE))
|
2006-10-31 12:23:14 +01:00
|
|
|
{
|
2017-02-10 19:30:37 +01:00
|
|
|
mysql_mutex_unlock(log_lock);
|
2016-09-22 08:26:45 +02:00
|
|
|
mysql_mutex_unlock(&data_lock);
|
2016-09-22 13:36:45 +02:00
|
|
|
sql_print_error("Failed when trying to open logs for '%s' in Relay_log_info::init(). Error: %M", ln, my_errno);
|
2006-10-31 12:23:14 +01:00
|
|
|
DBUG_RETURN(1);
|
|
|
|
}
|
2017-02-10 19:30:37 +01:00
|
|
|
mysql_mutex_unlock(log_lock);
|
2006-10-31 12:23:14 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
/* if file does not exist */
|
|
|
|
if (access(fname,F_OK))
|
|
|
|
{
|
|
|
|
/*
|
|
|
|
If someone removed the file from underneath our feet, just close
|
|
|
|
the old descriptor and re-create the old file
|
|
|
|
*/
|
|
|
|
if (info_fd >= 0)
|
2010-01-07 06:42:07 +01:00
|
|
|
mysql_file_close(info_fd, MYF(MY_WME));
|
|
|
|
if ((info_fd= mysql_file_open(key_file_relay_log_info,
|
|
|
|
fname, O_CREAT|O_RDWR|O_BINARY, MYF(MY_WME))) < 0)
|
2006-10-31 12:23:14 +01:00
|
|
|
{
|
2017-07-27 12:43:45 +02:00
|
|
|
sql_print_error("Failed to create a new relay log info file ("
|
|
|
|
"file '%s', errno %d)", fname, my_errno);
|
2013-06-15 17:32:08 +02:00
|
|
|
msg= current_thd->get_stmt_da()->message();
|
2006-10-31 12:23:14 +01:00
|
|
|
goto err;
|
|
|
|
}
|
2016-09-22 08:26:45 +02:00
|
|
|
if (init_io_cache(&info_file, info_fd, IO_SIZE*2, READ_CACHE, 0L,0,
|
2006-10-31 12:23:14 +01:00
|
|
|
MYF(MY_WME)))
|
|
|
|
{
|
|
|
|
sql_print_error("Failed to create a cache on relay log info file '%s'",
|
|
|
|
fname);
|
2013-06-15 17:32:08 +02:00
|
|
|
msg= current_thd->get_stmt_da()->message();
|
2006-10-31 12:23:14 +01:00
|
|
|
goto err;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Init relay log with first entry in the relay index file */
|
2016-09-22 08:26:45 +02:00
|
|
|
if (init_relay_log_pos(this,NullS,BIN_LOG_HEADER_SIZE,0 /* no data lock */,
|
2006-10-31 12:23:14 +01:00
|
|
|
&msg, 0))
|
|
|
|
{
|
|
|
|
sql_print_error("Failed to open the relay log 'FIRST' (relay_log_pos 4)");
|
|
|
|
goto err;
|
|
|
|
}
|
2016-09-22 08:26:45 +02:00
|
|
|
group_master_log_name[0]= 0;
|
|
|
|
group_master_log_pos= 0;
|
2006-10-31 12:23:14 +01:00
|
|
|
}
|
|
|
|
else // file exists
|
|
|
|
{
|
|
|
|
if (info_fd >= 0)
|
2016-09-22 08:26:45 +02:00
|
|
|
reinit_io_cache(&info_file, READ_CACHE, 0L,0,0);
|
2006-10-31 12:23:14 +01:00
|
|
|
else
|
|
|
|
{
|
|
|
|
int error=0;
|
2010-01-07 06:42:07 +01:00
|
|
|
if ((info_fd= mysql_file_open(key_file_relay_log_info,
|
|
|
|
fname, O_RDWR|O_BINARY, MYF(MY_WME))) < 0)
|
2006-10-31 12:23:14 +01:00
|
|
|
{
|
|
|
|
sql_print_error("\
|
|
|
|
Failed to open the existing relay log info file '%s' (errno %d)",
|
|
|
|
fname, my_errno);
|
|
|
|
error= 1;
|
|
|
|
}
|
2016-09-22 08:26:45 +02:00
|
|
|
else if (init_io_cache(&info_file, info_fd,
|
2006-10-31 12:23:14 +01:00
|
|
|
IO_SIZE*2, READ_CACHE, 0L, 0, MYF(MY_WME)))
|
|
|
|
{
|
|
|
|
sql_print_error("Failed to create a cache on relay log info file '%s'",
|
|
|
|
fname);
|
|
|
|
error= 1;
|
|
|
|
}
|
2018-04-04 11:16:12 +02:00
|
|
|
if (unlikely(error))
|
2006-10-31 12:23:14 +01:00
|
|
|
{
|
|
|
|
if (info_fd >= 0)
|
2010-01-07 06:42:07 +01:00
|
|
|
mysql_file_close(info_fd, MYF(0));
|
2016-09-22 08:26:45 +02:00
|
|
|
info_fd= -1;
|
2017-06-04 10:47:30 +02:00
|
|
|
mysql_mutex_lock(log_lock);
|
2016-09-22 08:26:45 +02:00
|
|
|
relay_log.close(LOG_CLOSE_INDEX | LOG_CLOSE_STOP_EVENT);
|
2017-06-04 10:47:30 +02:00
|
|
|
mysql_mutex_unlock(log_lock);
|
2016-09-22 08:26:45 +02:00
|
|
|
mysql_mutex_unlock(&data_lock);
|
2006-10-31 12:23:14 +01:00
|
|
|
DBUG_RETURN(1);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2014-06-24 14:43:08 +02:00
|
|
|
int relay_log_pos, master_log_pos, lines;
|
|
|
|
char *first_non_digit;
|
|
|
|
|
|
|
|
/*
|
|
|
|
Starting from MySQL 5.6.x, relay-log.info has a new format.
|
|
|
|
Now, its first line contains the number of lines in the file.
|
|
|
|
By reading this number we can determine which version our master.info
|
|
|
|
comes from. We can't simply count the lines in the file, since
|
|
|
|
versions before 5.6.x could generate files with more lines than
|
|
|
|
needed. If first line doesn't contain a number, or if it
|
|
|
|
contains a number less than LINES_IN_RELAY_LOG_INFO_WITH_DELAY,
|
|
|
|
then the file is treated like a file from pre-5.6.x version.
|
|
|
|
There is no ambiguity when reading an old master.info: before
|
|
|
|
5.6.x, the first line contained the binlog's name, which is
|
|
|
|
either empty or has an extension (contains a '.'), so can't be
|
|
|
|
confused with an integer.
|
|
|
|
|
|
|
|
So we're just reading first line and trying to figure which
|
|
|
|
version is this.
|
|
|
|
*/
|
|
|
|
|
|
|
|
/*
|
|
|
|
The first row is temporarily stored in mi->master_log_name, if
|
|
|
|
it is line count and not binlog name (new format) it will be
|
|
|
|
overwritten by the second row later.
|
|
|
|
*/
|
2016-09-22 08:26:45 +02:00
|
|
|
if (init_strvar_from_file(group_relay_log_name,
|
|
|
|
sizeof(group_relay_log_name),
|
|
|
|
&info_file, ""))
|
2014-06-24 14:43:08 +02:00
|
|
|
{
|
|
|
|
msg="Error reading slave log configuration";
|
|
|
|
goto err;
|
|
|
|
}
|
|
|
|
|
2016-09-22 08:26:45 +02:00
|
|
|
lines= strtoul(group_relay_log_name, &first_non_digit, 10);
|
2014-06-24 14:43:08 +02:00
|
|
|
|
2016-09-22 08:26:45 +02:00
|
|
|
if (group_relay_log_name[0] != '\0' &&
|
2014-06-24 14:43:08 +02:00
|
|
|
*first_non_digit == '\0' &&
|
|
|
|
lines >= LINES_IN_RELAY_LOG_INFO_WITH_DELAY)
|
|
|
|
{
|
|
|
|
DBUG_PRINT("info", ("relay_log_info file is in new format."));
|
|
|
|
/* Seems to be new format => read relay log name from next line */
|
2016-09-22 08:26:45 +02:00
|
|
|
if (init_strvar_from_file(group_relay_log_name,
|
|
|
|
sizeof(group_relay_log_name),
|
|
|
|
&info_file, ""))
|
2014-06-24 14:43:08 +02:00
|
|
|
{
|
|
|
|
msg="Error reading slave log configuration";
|
|
|
|
goto err;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
else
|
|
|
|
DBUG_PRINT("info", ("relay_log_info file is in old format."));
|
|
|
|
|
|
|
|
if (init_intvar_from_file(&relay_log_pos,
|
2016-09-22 08:26:45 +02:00
|
|
|
&info_file, BIN_LOG_HEADER_SIZE) ||
|
|
|
|
init_strvar_from_file(group_master_log_name,
|
|
|
|
sizeof(group_master_log_name),
|
|
|
|
&info_file, "") ||
|
|
|
|
init_intvar_from_file(&master_log_pos, &info_file, 0) ||
|
2014-06-24 14:43:08 +02:00
|
|
|
(lines >= LINES_IN_RELAY_LOG_INFO_WITH_DELAY &&
|
2016-09-22 08:26:45 +02:00
|
|
|
init_intvar_from_file(&sql_delay, &info_file, 0)))
|
2006-10-31 12:23:14 +01:00
|
|
|
{
|
|
|
|
msg="Error reading slave log configuration";
|
|
|
|
goto err;
|
|
|
|
}
|
2014-06-24 14:43:08 +02:00
|
|
|
|
2016-09-22 08:26:45 +02:00
|
|
|
strmake_buf(event_relay_log_name,group_relay_log_name);
|
|
|
|
group_relay_log_pos= event_relay_log_pos= relay_log_pos;
|
|
|
|
group_master_log_pos= master_log_pos;
|
2006-10-31 12:23:14 +01:00
|
|
|
|
2016-09-22 08:26:45 +02:00
|
|
|
if (is_relay_log_recovery && init_recovery(mi, &msg))
|
2009-09-30 23:41:05 +02:00
|
|
|
goto err;
|
|
|
|
|
2016-09-22 08:26:45 +02:00
|
|
|
relay_log_state.load(rpl_global_gtid_slave_state);
|
|
|
|
if (init_relay_log_pos(this,
|
|
|
|
group_relay_log_name,
|
|
|
|
group_relay_log_pos,
|
2006-10-31 12:23:14 +01:00
|
|
|
0 /* no data lock*/,
|
|
|
|
&msg, 0))
|
|
|
|
{
|
2015-08-25 17:29:58 +02:00
|
|
|
sql_print_error("Failed to open the relay log '%s' (relay_log_pos %llu)",
|
2016-09-22 08:26:45 +02:00
|
|
|
group_relay_log_name, group_relay_log_pos);
|
2006-10-31 12:23:14 +01:00
|
|
|
goto err;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2016-09-22 08:26:45 +02:00
|
|
|
DBUG_PRINT("info", ("my_b_tell(cur_log)=%llu event_relay_log_pos=%llu",
|
|
|
|
my_b_tell(cur_log), event_relay_log_pos));
|
|
|
|
DBUG_ASSERT(event_relay_log_pos >= BIN_LOG_HEADER_SIZE);
|
|
|
|
DBUG_ASSERT(my_b_tell(cur_log) == event_relay_log_pos);
|
2006-10-31 12:23:14 +01:00
|
|
|
|
|
|
|
/*
|
|
|
|
Now change the cache from READ to WRITE - must do this
|
2016-09-22 13:36:45 +02:00
|
|
|
before Relay_log_info::flush()
|
2006-10-31 12:23:14 +01:00
|
|
|
*/
|
2016-09-22 08:26:45 +02:00
|
|
|
reinit_io_cache(&info_file, WRITE_CACHE,0L,0,1);
|
2018-04-04 11:16:12 +02:00
|
|
|
if (unlikely((error= flush())))
|
2009-09-30 23:41:05 +02:00
|
|
|
{
|
|
|
|
msg= "Failed to flush relay log info file";
|
|
|
|
goto err;
|
|
|
|
}
|
2016-09-22 08:26:45 +02:00
|
|
|
if (count_relay_log_space(this))
|
2006-10-31 12:23:14 +01:00
|
|
|
{
|
|
|
|
msg="Error counting relay log space";
|
|
|
|
goto err;
|
|
|
|
}
|
2016-09-22 08:26:45 +02:00
|
|
|
inited= 1;
|
2017-08-17 11:32:16 +02:00
|
|
|
error_on_rli_init_info= false;
|
2016-09-22 08:26:45 +02:00
|
|
|
mysql_mutex_unlock(&data_lock);
|
2017-02-05 01:23:49 +01:00
|
|
|
DBUG_RETURN(0);
|
2006-10-31 12:23:14 +01:00
|
|
|
|
|
|
|
err:
|
2017-08-17 11:32:16 +02:00
|
|
|
error_on_rli_init_info= true;
|
2017-02-28 05:30:51 +01:00
|
|
|
if (msg)
|
|
|
|
sql_print_error("%s", msg);
|
2016-09-22 08:26:45 +02:00
|
|
|
end_io_cache(&info_file);
|
2006-10-31 12:23:14 +01:00
|
|
|
if (info_fd >= 0)
|
2010-01-07 06:42:07 +01:00
|
|
|
mysql_file_close(info_fd, MYF(0));
|
2016-09-22 08:26:45 +02:00
|
|
|
info_fd= -1;
|
2017-06-04 10:47:30 +02:00
|
|
|
mysql_mutex_lock(log_lock);
|
2016-09-22 08:26:45 +02:00
|
|
|
relay_log.close(LOG_CLOSE_INDEX | LOG_CLOSE_STOP_EVENT);
|
2017-06-04 10:47:30 +02:00
|
|
|
mysql_mutex_unlock(log_lock);
|
2016-09-22 08:26:45 +02:00
|
|
|
mysql_mutex_unlock(&data_lock);
|
2006-10-31 12:23:14 +01:00
|
|
|
DBUG_RETURN(1);
|
|
|
|
}
|
|
|
|
|
|
|
|
|
2007-08-16 07:37:50 +02:00
|
|
|
static inline int add_relay_log(Relay_log_info* rli,LOG_INFO* linfo)
|
2006-10-31 12:23:14 +01:00
|
|
|
{
|
|
|
|
MY_STAT s;
|
|
|
|
DBUG_ENTER("add_relay_log");
|
2011-03-01 17:39:28 +01:00
|
|
|
if (!mysql_file_stat(key_file_relaylog,
|
2010-01-07 06:42:07 +01:00
|
|
|
linfo->log_file_name, &s, MYF(0)))
|
2006-10-31 12:23:14 +01:00
|
|
|
{
|
|
|
|
sql_print_error("log %s listed in the index, but failed to stat",
|
|
|
|
linfo->log_file_name);
|
|
|
|
DBUG_RETURN(1);
|
|
|
|
}
|
|
|
|
rli->log_space_total += s.st_size;
|
2015-08-25 17:29:58 +02:00
|
|
|
DBUG_PRINT("info",("log_space_total: %llu", rli->log_space_total));
|
2006-10-31 12:23:14 +01:00
|
|
|
DBUG_RETURN(0);
|
|
|
|
}
|
|
|
|
|
|
|
|
|
2007-08-16 07:37:50 +02:00
|
|
|
static int count_relay_log_space(Relay_log_info* rli)
|
2006-10-31 12:23:14 +01:00
|
|
|
{
|
|
|
|
LOG_INFO linfo;
|
|
|
|
DBUG_ENTER("count_relay_log_space");
|
|
|
|
rli->log_space_total= 0;
|
|
|
|
if (rli->relay_log.find_log_pos(&linfo, NullS, 1))
|
|
|
|
{
|
|
|
|
sql_print_error("Could not find first log while counting relay log space");
|
|
|
|
DBUG_RETURN(1);
|
|
|
|
}
|
|
|
|
do
|
|
|
|
{
|
|
|
|
if (add_relay_log(rli,&linfo))
|
|
|
|
DBUG_RETURN(1);
|
|
|
|
} while (!rli->relay_log.find_next_log(&linfo, 1));
|
|
|
|
/*
|
|
|
|
As we have counted everything, including what may have written in a
|
|
|
|
preceding write, we must reset bytes_written, or we may count some space
|
|
|
|
twice.
|
|
|
|
*/
|
|
|
|
rli->relay_log.reset_bytes_written();
|
|
|
|
DBUG_RETURN(0);
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
/*
|
2007-08-16 07:37:50 +02:00
|
|
|
Reset UNTIL condition for Relay_log_info
|
2006-10-31 12:23:14 +01:00
|
|
|
|
|
|
|
SYNOPSYS
|
|
|
|
clear_until_condition()
|
2007-08-16 07:37:50 +02:00
|
|
|
rli - Relay_log_info structure where UNTIL condition should be reset
|
2006-10-31 12:23:14 +01:00
|
|
|
*/
|
|
|
|
|
2007-08-16 07:37:50 +02:00
|
|
|
void Relay_log_info::clear_until_condition()
|
2006-10-31 12:23:14 +01:00
|
|
|
{
|
|
|
|
DBUG_ENTER("clear_until_condition");
|
|
|
|
|
2007-08-16 07:37:50 +02:00
|
|
|
until_condition= Relay_log_info::UNTIL_NONE;
|
2006-10-31 12:23:14 +01:00
|
|
|
until_log_name[0]= 0;
|
|
|
|
until_log_pos= 0;
|
|
|
|
DBUG_VOID_RETURN;
|
|
|
|
}
|
|
|
|
|
|
|
|
|
2014-11-13 10:09:46 +01:00
|
|
|
/*
|
|
|
|
Read the correct format description event for starting to replicate from
|
|
|
|
a given position in a relay log file.
|
|
|
|
*/
|
|
|
|
Format_description_log_event *
|
|
|
|
read_relay_log_description_event(IO_CACHE *cur_log, ulonglong start_pos,
|
|
|
|
const char **errmsg)
|
|
|
|
{
|
|
|
|
Log_event *ev;
|
|
|
|
Format_description_log_event *fdev;
|
|
|
|
bool found= false;
|
|
|
|
|
|
|
|
/*
|
|
|
|
By default the relay log is in binlog format 3 (4.0).
|
|
|
|
Even if format is 4, this will work enough to read the first event
|
|
|
|
(Format_desc) (remember that format 4 is just lenghtened compared to format
|
|
|
|
3; format 3 is a prefix of format 4).
|
|
|
|
*/
|
|
|
|
fdev= new Format_description_log_event(3);
|
|
|
|
|
|
|
|
while (!found)
|
|
|
|
{
|
|
|
|
Log_event_type typ;
|
|
|
|
|
|
|
|
/*
|
|
|
|
Read the possible Format_description_log_event; if position
|
|
|
|
was 4, no need, it will be read naturally.
|
|
|
|
*/
|
|
|
|
DBUG_PRINT("info",("looking for a Format_description_log_event"));
|
|
|
|
|
|
|
|
if (my_b_tell(cur_log) >= start_pos)
|
|
|
|
break;
|
|
|
|
|
2017-10-26 11:46:45 +02:00
|
|
|
if (!(ev= Log_event::read_log_event(cur_log, fdev,
|
2014-11-13 10:09:46 +01:00
|
|
|
opt_slave_sql_verify_checksum)))
|
|
|
|
{
|
|
|
|
DBUG_PRINT("info",("could not read event, cur_log->error=%d",
|
|
|
|
cur_log->error));
|
|
|
|
if (cur_log->error) /* not EOF */
|
|
|
|
{
|
|
|
|
*errmsg= "I/O error reading event at position 4";
|
|
|
|
delete fdev;
|
|
|
|
return NULL;
|
|
|
|
}
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
typ= ev->get_type_code();
|
|
|
|
if (typ == FORMAT_DESCRIPTION_EVENT)
|
|
|
|
{
|
2015-09-02 09:58:08 +02:00
|
|
|
Format_description_log_event *old= fdev;
|
2014-11-13 10:09:46 +01:00
|
|
|
DBUG_PRINT("info",("found Format_description_log_event"));
|
|
|
|
fdev= (Format_description_log_event*) ev;
|
2015-09-02 09:58:08 +02:00
|
|
|
fdev->copy_crypto_data(old);
|
|
|
|
delete old;
|
|
|
|
|
2014-11-13 10:09:46 +01:00
|
|
|
/*
|
|
|
|
As ev was returned by read_log_event, it has passed is_valid(), so
|
|
|
|
my_malloc() in ctor worked, no need to check again.
|
|
|
|
*/
|
|
|
|
/*
|
|
|
|
Ok, we found a Format_description event. But it is not sure that this
|
|
|
|
describes the whole relay log; indeed, one can have this sequence
|
|
|
|
(starting from position 4):
|
|
|
|
Format_desc (of slave)
|
|
|
|
Rotate (of master)
|
|
|
|
Format_desc (of master)
|
|
|
|
So the Format_desc which really describes the rest of the relay log
|
|
|
|
is the 3rd event (it can't be further than that, because we rotate
|
|
|
|
the relay log when we queue a Rotate event from the master).
|
|
|
|
But what describes the Rotate is the first Format_desc.
|
|
|
|
So what we do is:
|
|
|
|
go on searching for Format_description events, until you exceed the
|
|
|
|
position (argument 'pos') or until you find another event than Rotate
|
|
|
|
or Format_desc.
|
|
|
|
*/
|
|
|
|
}
|
2015-09-02 09:58:08 +02:00
|
|
|
else if (typ == START_ENCRYPTION_EVENT)
|
|
|
|
{
|
|
|
|
if (fdev->start_decryption((Start_encryption_log_event*) ev))
|
|
|
|
{
|
|
|
|
*errmsg= "Unable to set up decryption of binlog.";
|
|
|
|
delete ev;
|
|
|
|
delete fdev;
|
|
|
|
return NULL;
|
|
|
|
}
|
|
|
|
delete ev;
|
|
|
|
}
|
2014-11-13 10:09:46 +01:00
|
|
|
else
|
|
|
|
{
|
|
|
|
DBUG_PRINT("info",("found event of another type=%d", typ));
|
|
|
|
found= (typ != ROTATE_EVENT);
|
|
|
|
delete ev;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
return fdev;
|
|
|
|
}
|
|
|
|
|
|
|
|
|
2006-10-31 12:23:14 +01:00
|
|
|
/*
|
|
|
|
Open the given relay log
|
|
|
|
|
|
|
|
SYNOPSIS
|
|
|
|
init_relay_log_pos()
|
|
|
|
rli Relay information (will be initialized)
|
|
|
|
log Name of relay log file to read from. NULL = First log
|
|
|
|
pos Position in relay log file
|
|
|
|
need_data_lock Set to 1 if this functions should do mutex locks
|
|
|
|
errmsg Store pointer to error message here
|
|
|
|
look_for_description_event
|
|
|
|
1 if we should look for such an event. We only need
|
|
|
|
this when the SQL thread starts and opens an existing
|
|
|
|
relay log and has to execute it (possibly from an
|
|
|
|
offset >4); then we need to read the first event of
|
|
|
|
the relay log to be able to parse the events we have
|
|
|
|
to execute.
|
|
|
|
|
|
|
|
DESCRIPTION
|
|
|
|
- Close old open relay log files.
|
|
|
|
- If we are using the same relay log as the running IO-thread, then set
|
|
|
|
rli->cur_log to point to the same IO_CACHE entry.
|
|
|
|
- If not, open the 'log' binary file.
|
|
|
|
|
|
|
|
TODO
|
|
|
|
- check proper initialization of group_master_log_name/group_master_log_pos
|
|
|
|
|
|
|
|
RETURN VALUES
|
|
|
|
0 ok
|
|
|
|
1 error. errmsg is set to point to the error message
|
|
|
|
*/
|
|
|
|
|
2007-08-16 07:37:50 +02:00
|
|
|
int init_relay_log_pos(Relay_log_info* rli,const char* log,
|
2006-10-31 12:23:14 +01:00
|
|
|
ulonglong pos, bool need_data_lock,
|
|
|
|
const char** errmsg,
|
|
|
|
bool look_for_description_event)
|
|
|
|
{
|
|
|
|
DBUG_ENTER("init_relay_log_pos");
|
2006-11-27 00:47:38 +01:00
|
|
|
DBUG_PRINT("info", ("pos: %lu", (ulong) pos));
|
2006-10-31 12:23:14 +01:00
|
|
|
|
|
|
|
*errmsg=0;
|
2010-01-07 06:42:07 +01:00
|
|
|
mysql_mutex_t *log_lock= rli->relay_log.get_log_lock();
|
2006-10-31 12:23:14 +01:00
|
|
|
|
|
|
|
if (need_data_lock)
|
2010-01-07 06:42:07 +01:00
|
|
|
mysql_mutex_lock(&rli->data_lock);
|
2006-10-31 12:23:14 +01:00
|
|
|
|
|
|
|
/*
|
|
|
|
Slave threads are not the only users of init_relay_log_pos(). CHANGE MASTER
|
|
|
|
is, too, and init_slave() too; these 2 functions allocate a description
|
|
|
|
event in init_relay_log_pos, which is not freed by the terminating SQL slave
|
|
|
|
thread as that thread is not started by these functions. So we have to free
|
|
|
|
the description_event here, in case, so that there is no memory leak in
|
|
|
|
running, say, CHANGE MASTER.
|
|
|
|
*/
|
|
|
|
delete rli->relay_log.description_event_for_exec;
|
|
|
|
/*
|
|
|
|
By default the relay log is in binlog format 3 (4.0).
|
|
|
|
Even if format is 4, this will work enough to read the first event
|
|
|
|
(Format_desc) (remember that format 4 is just lenghtened compared to format
|
|
|
|
3; format 3 is a prefix of format 4).
|
|
|
|
*/
|
|
|
|
rli->relay_log.description_event_for_exec= new
|
|
|
|
Format_description_log_event(3);
|
|
|
|
|
2010-01-07 06:42:07 +01:00
|
|
|
mysql_mutex_lock(log_lock);
|
2006-10-31 12:23:14 +01:00
|
|
|
|
|
|
|
/* Close log file and free buffers if it's already open */
|
|
|
|
if (rli->cur_log_fd >= 0)
|
|
|
|
{
|
|
|
|
end_io_cache(&rli->cache_buf);
|
2010-01-07 06:42:07 +01:00
|
|
|
mysql_file_close(rli->cur_log_fd, MYF(MY_WME));
|
2006-10-31 12:23:14 +01:00
|
|
|
rli->cur_log_fd = -1;
|
|
|
|
}
|
|
|
|
|
|
|
|
rli->group_relay_log_pos = rli->event_relay_log_pos = pos;
|
Fixes for parallel slave:
- Made slaves temporary table multi-thread slave safe by adding mutex around save_temporary_table usage.
- rli->save_temporary_tables is the active list of all used temporary tables
- This is copied to THD->temporary_tables when temporary tables are opened and updated when temporary tables are closed
- Added THD->lock_temporary_tables() and THD->unlock_temporary_tables() to simplify this.
- Relay_log_info->sql_thd renamed to Relay_log_info->sql_driver_thd to avoid wrong usage for merged code.
- Added is_part_of_group() to mark functions that are part of the next function. This replaces setting IN_STMT when events are executed.
- Added is_begin(), is_commit() and is_rollback() functions to Query_log_event to simplify code.
- If slave_skip_counter is set run things in single threaded mode. This simplifies code for skipping events.
- Updating state of relay log (IN_STMT and IN_TRANSACTION) is moved to one single function: update_state_of_relay_log()
We can't use OPTION_BEGIN to check for the state anymore as the sql_driver and sql execution threads may be different.
Clear IN_STMT and IN_TRANSACTION in init_relay_log_pos() and Relay_log_info::cleanup_context() to ensure the flags doesn't survive slave restarts
is_in_group() is now independent of state of executed transaction.
- Reset thd->transaction.all.modified_non_trans_table() if we did set it for single table row events.
This was mainly for keeping the flag as documented.
- Changed slave_open_temp_tables to uint32 to be able to use atomic operators on it.
- Relay_log_info::sleep_lock -> rpl_group_info::sleep_lock
- Relay_log_info::sleep_cond -> rpl_group_info::sleep_cond
- Changed some functions to take rpl_group_info instead of Relay_log_info to make them multi-slave safe and to simplify usage
- do_shall_skip()
- continue_group()
- sql_slave_killed()
- next_event()
- Simplifed arguments to io_salve_killed(), check_io_slave_killed() and sql_slave_killed(); No reason to supply THD as this is part of the given structure.
- set_thd_in_use_temporary_tables() removed as in_use is set on usage
- Added information to thd_proc_info() which thread is waiting for slave mutex to exit.
- In open_table() reuse code from find_temporary_table()
Other things:
- More DBUG statements
- Fixed the rpl_incident.test can be run with --debug
- More comments
- Disabled not used function rpl_connect_master()
mysql-test/suite/perfschema/r/all_instances.result:
Moved sleep_lock and sleep_cond to rpl_group_info
mysql-test/suite/rpl/r/rpl_incident.result:
Updated result
mysql-test/suite/rpl/t/rpl_incident-master.opt:
Not needed anymore
mysql-test/suite/rpl/t/rpl_incident.test:
Fixed that test can be run with --debug
sql/handler.cc:
More DBUG_PRINT
sql/log.cc:
More comments
sql/log_event.cc:
Added DBUG statements
do_shall_skip(), continue_group() now takes rpl_group_info param
Use is_begin(), is_commit() and is_rollback() functions instead of inspecting query string
We don't have set slaves temporary tables 'in_use' as this is now done when tables are opened.
Removed IN_STMT flag setting. This is now done in update_state_of_relay_log()
Use IN_TRANSACTION flag to test state of relay log.
In rows_event_stmt_cleanup() reset thd->transaction.all.modified_non_trans_table if we had set this before.
sql/log_event.h:
do_shall_skip(), continue_group() now takes rpl_group_info param
Added is_part_of_group() to mark events that are part of the next event. This replaces setting IN_STMT when events are executed.
Added is_begin(), is_commit() and is_rollback() functions to Query_log_event to simplify code.
sql/log_event_old.cc:
Removed IN_STMT flag setting. This is now done in update_state_of_relay_log()
do_shall_skip(), continue_group() now takes rpl_group_info param
sql/log_event_old.h:
Added is_part_of_group() to mark events that are part of the next event.
do_shall_skip(), continue_group() now takes rpl_group_info param
sql/mysqld.cc:
Changed slave_open_temp_tables to uint32 to be able to use atomic operators on it.
Relay_log_info::sleep_lock -> Rpl_group_info::sleep_lock
Relay_log_info::sleep_cond -> Rpl_group_info::sleep_cond
sql/mysqld.h:
Updated types and names
sql/rpl_gtid.cc:
More DBUG
sql/rpl_parallel.cc:
Updated TODO section
Set thd for event that is execution
Use new is_begin(), is_commit() and is_rollback() functions.
More comments
sql/rpl_rli.cc:
sql_thd -> sql_driver_thd
Relay_log_info::sleep_lock -> rpl_group_info::sleep_lock
Relay_log_info::sleep_cond -> rpl_group_info::sleep_cond
Clear IN_STMT and IN_TRANSACTION in init_relay_log_pos() and Relay_log_info::cleanup_context() to ensure the flags doesn't survive slave restarts.
Reset table->in_use for temporary tables as the table may have been used by another THD.
Use IN_TRANSACTION instead of OPTION_BEGIN to check state of relay log.
Removed IN_STMT flag setting. This is now done in update_state_of_relay_log()
sql/rpl_rli.h:
Changed relay log state flags to bit masks instead of bit positions (most other code we have uses bit masks)
Added IN_TRANSACTION to mark if we are in a BEGIN ... COMMIT section.
save_temporary_tables is now thread safe
Relay_log_info::sleep_lock -> rpl_group_info::sleep_lock
Relay_log_info::sleep_cond -> rpl_group_info::sleep_cond
Relay_log_info->sql_thd renamed to Relay_log_info->sql_driver_thd to avoid wrong usage for merged code
is_in_group() is now independent of state of executed transaction.
sql/slave.cc:
Simplifed arguments to io_salve_killed(), sql_slave_killed() and check_io_slave_killed(); No reason to supply THD as this is part of the given structure.
set_thd_in_use_temporary_tables() removed as in_use is set on usage in sql_base.cc
sql_thd -> sql_driver_thd
More DBUG
Added update_state_of_relay_log() which will calculate the IN_STMT and IN_TRANSACTION state of the relay log after the current element is executed.
If slave_skip_counter is set run things in single threaded mode.
Simplifed arguments to io_salve_killed(), check_io_slave_killed() and sql_slave_killed(); No reason to supply THD as this is part of the given structure.
Added information to thd_proc_info() which thread is waiting for slave mutex to exit.
Disabled not used function rpl_connect_master()
Updated argument to next_event()
sql/sql_base.cc:
Added mutex around usage of slave's temporary tables. The active list is always kept up to date in sql->rgi_slave->save_temporary_tables.
Clear thd->temporary_tables after query (safety)
More DBUG
When using temporary table, set table->in_use to current thd as the THD may be different for slave threads.
Some code is ifdef:ed with REMOVE_AFTER_MERGE_WITH_10 as the given code in 10.0 is not yet in this tree.
In open_table() reuse code from find_temporary_table()
sql/sql_binlog.cc:
rli->sql_thd -> rli->sql_driver_thd
Remove duplicate setting of rgi->rli
sql/sql_class.cc:
Added helper functions rgi_lock_temporary_tables() and rgi_unlock_temporary_tables()
Would have been nicer to have these inline, but there was no easy way to do that
sql/sql_class.h:
Added functions to protect slaves temporary tables
sql/sql_parse.cc:
Added DBUG_PRINT
sql/transaction.cc:
Added comment
2013-10-13 23:24:05 +02:00
|
|
|
rli->clear_flag(Relay_log_info::IN_STMT);
|
|
|
|
rli->clear_flag(Relay_log_info::IN_TRANSACTION);
|
2006-10-31 12:23:14 +01:00
|
|
|
|
|
|
|
/*
|
|
|
|
Test to see if the previous run was with the skip of purging
|
|
|
|
If yes, we do not purge when we restart
|
|
|
|
*/
|
|
|
|
if (rli->relay_log.find_log_pos(&rli->linfo, NullS, 1))
|
|
|
|
{
|
|
|
|
*errmsg="Could not find first log during relay log initialization";
|
|
|
|
goto err;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (log && rli->relay_log.find_log_pos(&rli->linfo, log, 1))
|
|
|
|
{
|
|
|
|
*errmsg="Could not find target log during relay log initialization";
|
|
|
|
goto err;
|
|
|
|
}
|
2013-04-17 19:42:34 +02:00
|
|
|
strmake_buf(rli->group_relay_log_name,rli->linfo.log_file_name);
|
|
|
|
strmake_buf(rli->event_relay_log_name,rli->linfo.log_file_name);
|
2006-10-31 12:23:14 +01:00
|
|
|
if (rli->relay_log.is_active(rli->linfo.log_file_name))
|
|
|
|
{
|
|
|
|
/*
|
|
|
|
The IO thread is using this log file.
|
|
|
|
In this case, we will use the same IO_CACHE pointer to
|
|
|
|
read data as the IO thread is using to write data.
|
|
|
|
*/
|
|
|
|
my_b_seek((rli->cur_log=rli->relay_log.get_log_file()), (off_t)0);
|
|
|
|
if (check_binlog_magic(rli->cur_log,errmsg))
|
|
|
|
goto err;
|
|
|
|
rli->cur_log_old_open_count=rli->relay_log.get_open_count();
|
|
|
|
}
|
|
|
|
else
|
|
|
|
{
|
|
|
|
/*
|
|
|
|
Open the relay log and set rli->cur_log to point at this one
|
|
|
|
*/
|
|
|
|
if ((rli->cur_log_fd=open_binlog(&rli->cache_buf,
|
|
|
|
rli->linfo.log_file_name,errmsg)) < 0)
|
|
|
|
goto err;
|
|
|
|
rli->cur_log = &rli->cache_buf;
|
|
|
|
}
|
|
|
|
/*
|
|
|
|
In all cases, check_binlog_magic() has been called so we're at offset 4 for
|
|
|
|
sure.
|
|
|
|
*/
|
|
|
|
if (pos > BIN_LOG_HEADER_SIZE) /* If pos<=4, we stay at 4 */
|
|
|
|
{
|
2014-11-13 10:09:46 +01:00
|
|
|
if (look_for_description_event)
|
2006-10-31 12:23:14 +01:00
|
|
|
{
|
2014-11-13 10:09:46 +01:00
|
|
|
Format_description_log_event *fdev;
|
|
|
|
if (!(fdev= read_relay_log_description_event(rli->cur_log, pos, errmsg)))
|
|
|
|
goto err;
|
|
|
|
delete rli->relay_log.description_event_for_exec;
|
|
|
|
rli->relay_log.description_event_for_exec= fdev;
|
2006-10-31 12:23:14 +01:00
|
|
|
}
|
|
|
|
my_b_seek(rli->cur_log,(off_t)pos);
|
2015-08-25 17:29:58 +02:00
|
|
|
DBUG_PRINT("info", ("my_b_tell(rli->cur_log)=%llu rli->event_relay_log_pos=%llu",
|
|
|
|
my_b_tell(rli->cur_log), rli->event_relay_log_pos));
|
2006-10-31 12:23:14 +01:00
|
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
err:
|
|
|
|
/*
|
|
|
|
If we don't purge, we can't honour relay_log_space_limit ;
|
|
|
|
silently discard it
|
|
|
|
*/
|
|
|
|
if (!relay_log_purge)
|
|
|
|
rli->log_space_limit= 0;
|
2010-01-07 06:42:07 +01:00
|
|
|
mysql_cond_broadcast(&rli->data_cond);
|
2006-10-31 12:23:14 +01:00
|
|
|
|
2010-01-07 06:42:07 +01:00
|
|
|
mysql_mutex_unlock(log_lock);
|
2006-10-31 12:23:14 +01:00
|
|
|
|
|
|
|
if (need_data_lock)
|
2010-01-07 06:42:07 +01:00
|
|
|
mysql_mutex_unlock(&rli->data_lock);
|
2006-10-31 12:23:14 +01:00
|
|
|
if (!rli->relay_log.description_event_for_exec->is_valid() && !*errmsg)
|
|
|
|
*errmsg= "Invalid Format_description log event; could be out of memory";
|
|
|
|
|
2016-09-22 08:26:45 +02:00
|
|
|
DBUG_PRINT("info", ("Returning %d from init_relay_log_pos", (*errmsg)?1:0));
|
|
|
|
|
2006-10-31 12:23:14 +01:00
|
|
|
DBUG_RETURN ((*errmsg) ? 1 : 0);
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
Waits until the SQL thread reaches (has executed up to) the
|
|
|
|
log/position or timed out.
|
|
|
|
|
|
|
|
SYNOPSIS
|
|
|
|
wait_for_pos()
|
|
|
|
thd client thread that sent SELECT MASTER_POS_WAIT
|
|
|
|
log_name log name to wait for
|
|
|
|
log_pos position to wait for
|
|
|
|
timeout timeout in seconds before giving up waiting
|
|
|
|
|
|
|
|
NOTES
|
|
|
|
timeout is longlong whereas it should be ulong ; but this is
|
|
|
|
to catch if the user submitted a negative timeout.
|
|
|
|
|
|
|
|
RETURN VALUES
|
|
|
|
-2 improper arguments (log_pos<0)
|
|
|
|
or slave not running, or master info changed
|
|
|
|
during the function's execution,
|
|
|
|
or client thread killed. -2 is translated to NULL by caller
|
|
|
|
-1 timed out
|
|
|
|
>=0 number of log events the function had to wait
|
|
|
|
before reaching the desired log/position
|
|
|
|
*/
|
|
|
|
|
2007-08-16 07:37:50 +02:00
|
|
|
int Relay_log_info::wait_for_pos(THD* thd, String* log_name,
|
2006-10-31 12:23:14 +01:00
|
|
|
longlong log_pos,
|
|
|
|
longlong timeout)
|
|
|
|
{
|
|
|
|
int event_count = 0;
|
|
|
|
ulong init_abort_pos_wait;
|
|
|
|
int error=0;
|
|
|
|
struct timespec abstime; // for timeout checking
|
fixes for test failures
and small collateral changes
mysql-test/lib/My/Test.pm:
somehow with "print" we get truncated writes sometimes
mysql-test/suite/perfschema/r/digest_table_full.result:
md5 hashes of statement digests differ, because yacc token codes are different in mariadb
mysql-test/suite/perfschema/r/dml_handler.result:
host table is not ported over yet
mysql-test/suite/perfschema/r/information_schema.result:
host table is not ported over yet
mysql-test/suite/perfschema/r/nesting.result:
this differs, because we don't rewrite general log queries, and multi-statement
packets are logged as a one entry. this result file is identical to what mysql-5.6.5
produces with the --log-raw option.
mysql-test/suite/perfschema/r/relaylog.result:
MariaDB modifies the binlog index file directly, while MySQL 5.6 has a feature "crash-safe binlog index" and modifies a special "crash-safe" shadow copy of the index file and then moves it over. That's why this test shows "NONE" index file writes in MySQL and "MANY" in MariaDB.
mysql-test/suite/perfschema/r/server_init.result:
MariaDB initializes the "manager" resources from the "manager" thread, and starts this thread only when --flush-time is not 0. MySQL 5.6 initializes "manager" resources unconditionally on server startup.
mysql-test/suite/perfschema/r/stage_mdl_global.result:
this differs, because MariaDB disables query cache when query_cache_size=0. MySQL does not
do that, and this causes useless mutex locks and waits.
mysql-test/suite/perfschema/r/statement_digest.result:
md5 hashes of statement digests differ, because yacc token codes are different in mariadb
mysql-test/suite/perfschema/r/statement_digest_consumers.result:
md5 hashes of statement digests differ, because yacc token codes are different in mariadb
mysql-test/suite/perfschema/r/statement_digest_long_query.result:
md5 hashes of statement digests differ, because yacc token codes are different in mariadb
mysql-test/suite/rpl/r/rpl_mixed_drop_create_temp_table.result:
will be updated to match 5.6 when alfranio.correia@oracle.com-20110512172919-c1b5kmum4h52g0ni and anders.song@greatopensource.com-20110105052107-zoab0bsf5a6xxk2y are merged
mysql-test/suite/rpl/r/rpl_non_direct_mixed_mixing_engines.result:
will be updated to match 5.6 when anders.song@greatopensource.com-20110105052107-zoab0bsf5a6xxk2y is merged
2012-09-27 20:09:46 +02:00
|
|
|
PSI_stage_info old_stage;
|
2007-08-16 07:37:50 +02:00
|
|
|
DBUG_ENTER("Relay_log_info::wait_for_pos");
|
2006-10-31 12:23:14 +01:00
|
|
|
|
|
|
|
if (!inited)
|
2008-03-14 17:52:57 +01:00
|
|
|
DBUG_RETURN(-2);
|
2006-10-31 12:23:14 +01:00
|
|
|
|
|
|
|
DBUG_PRINT("enter",("log_name: '%s' log_pos: %lu timeout: %lu",
|
|
|
|
log_name->c_ptr(), (ulong) log_pos, (ulong) timeout));
|
|
|
|
|
|
|
|
set_timespec(abstime,timeout);
|
2010-01-07 06:42:07 +01:00
|
|
|
mysql_mutex_lock(&data_lock);
|
fixes for test failures
and small collateral changes
mysql-test/lib/My/Test.pm:
somehow with "print" we get truncated writes sometimes
mysql-test/suite/perfschema/r/digest_table_full.result:
md5 hashes of statement digests differ, because yacc token codes are different in mariadb
mysql-test/suite/perfschema/r/dml_handler.result:
host table is not ported over yet
mysql-test/suite/perfschema/r/information_schema.result:
host table is not ported over yet
mysql-test/suite/perfschema/r/nesting.result:
this differs, because we don't rewrite general log queries, and multi-statement
packets are logged as a one entry. this result file is identical to what mysql-5.6.5
produces with the --log-raw option.
mysql-test/suite/perfschema/r/relaylog.result:
MariaDB modifies the binlog index file directly, while MySQL 5.6 has a feature "crash-safe binlog index" and modifies a special "crash-safe" shadow copy of the index file and then moves it over. That's why this test shows "NONE" index file writes in MySQL and "MANY" in MariaDB.
mysql-test/suite/perfschema/r/server_init.result:
MariaDB initializes the "manager" resources from the "manager" thread, and starts this thread only when --flush-time is not 0. MySQL 5.6 initializes "manager" resources unconditionally on server startup.
mysql-test/suite/perfschema/r/stage_mdl_global.result:
this differs, because MariaDB disables query cache when query_cache_size=0. MySQL does not
do that, and this causes useless mutex locks and waits.
mysql-test/suite/perfschema/r/statement_digest.result:
md5 hashes of statement digests differ, because yacc token codes are different in mariadb
mysql-test/suite/perfschema/r/statement_digest_consumers.result:
md5 hashes of statement digests differ, because yacc token codes are different in mariadb
mysql-test/suite/perfschema/r/statement_digest_long_query.result:
md5 hashes of statement digests differ, because yacc token codes are different in mariadb
mysql-test/suite/rpl/r/rpl_mixed_drop_create_temp_table.result:
will be updated to match 5.6 when alfranio.correia@oracle.com-20110512172919-c1b5kmum4h52g0ni and anders.song@greatopensource.com-20110105052107-zoab0bsf5a6xxk2y are merged
mysql-test/suite/rpl/r/rpl_non_direct_mixed_mixing_engines.result:
will be updated to match 5.6 when anders.song@greatopensource.com-20110105052107-zoab0bsf5a6xxk2y is merged
2012-09-27 20:09:46 +02:00
|
|
|
thd->ENTER_COND(&data_cond, &data_lock,
|
|
|
|
&stage_waiting_for_the_slave_thread_to_advance_position,
|
|
|
|
&old_stage);
|
2006-10-31 12:23:14 +01:00
|
|
|
/*
|
|
|
|
This function will abort when it notices that some CHANGE MASTER or
|
|
|
|
RESET MASTER has changed the master info.
|
|
|
|
To catch this, these commands modify abort_pos_wait ; We just monitor
|
|
|
|
abort_pos_wait and see if it has changed.
|
|
|
|
Why do we have this mechanism instead of simply monitoring slave_running
|
|
|
|
in the loop (we do this too), as CHANGE MASTER/RESET SLAVE require that
|
|
|
|
the SQL thread be stopped?
|
|
|
|
This is becasue if someones does:
|
|
|
|
STOP SLAVE;CHANGE MASTER/RESET SLAVE; START SLAVE;
|
|
|
|
the change may happen very quickly and we may not notice that
|
|
|
|
slave_running briefly switches between 1/0/1.
|
|
|
|
*/
|
|
|
|
init_abort_pos_wait= abort_pos_wait;
|
|
|
|
|
|
|
|
/*
|
|
|
|
We'll need to
|
|
|
|
handle all possible log names comparisons (e.g. 999 vs 1000).
|
|
|
|
We use ulong for string->number conversion ; this is no
|
|
|
|
stronger limitation than in find_uniq_filename in sql/log.cc
|
|
|
|
*/
|
|
|
|
ulong log_name_extension;
|
|
|
|
char log_name_tmp[FN_REFLEN]; //make a char[] from String
|
|
|
|
|
2013-03-25 23:03:13 +01:00
|
|
|
strmake(log_name_tmp, log_name->ptr(), MY_MIN(log_name->length(), FN_REFLEN-1));
|
2006-10-31 12:23:14 +01:00
|
|
|
|
|
|
|
char *p= fn_ext(log_name_tmp);
|
|
|
|
char *p_end;
|
|
|
|
if (!*p || log_pos<0)
|
|
|
|
{
|
|
|
|
error= -2; //means improper arguments
|
|
|
|
goto err;
|
|
|
|
}
|
|
|
|
// Convert 0-3 to 4
|
2013-03-25 23:03:13 +01:00
|
|
|
log_pos= MY_MAX(log_pos, BIN_LOG_HEADER_SIZE);
|
2006-10-31 12:23:14 +01:00
|
|
|
/* p points to '.' */
|
|
|
|
log_name_extension= strtoul(++p, &p_end, 10);
|
|
|
|
/*
|
|
|
|
p_end points to the first invalid character.
|
|
|
|
If it equals to p, no digits were found, error.
|
|
|
|
If it contains '\0' it means conversion went ok.
|
|
|
|
*/
|
|
|
|
if (p_end==p || *p_end)
|
|
|
|
{
|
|
|
|
error= -2;
|
|
|
|
goto err;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* The "compare and wait" main loop */
|
|
|
|
while (!thd->killed &&
|
|
|
|
init_abort_pos_wait == abort_pos_wait &&
|
|
|
|
slave_running)
|
|
|
|
{
|
|
|
|
bool pos_reached;
|
|
|
|
int cmp_result= 0;
|
|
|
|
|
|
|
|
DBUG_PRINT("info",
|
|
|
|
("init_abort_pos_wait: %ld abort_pos_wait: %ld",
|
|
|
|
init_abort_pos_wait, abort_pos_wait));
|
|
|
|
DBUG_PRINT("info",("group_master_log_name: '%s' pos: %lu",
|
|
|
|
group_master_log_name, (ulong) group_master_log_pos));
|
|
|
|
|
|
|
|
/*
|
|
|
|
group_master_log_name can be "", if we are just after a fresh
|
|
|
|
replication start or after a CHANGE MASTER TO MASTER_HOST/PORT
|
|
|
|
(before we have executed one Rotate event from the master) or
|
|
|
|
(rare) if the user is doing a weird slave setup (see next
|
|
|
|
paragraph). If group_master_log_name is "", we assume we don't
|
|
|
|
have enough info to do the comparison yet, so we just wait until
|
|
|
|
more data. In this case master_log_pos is always 0 except if
|
|
|
|
somebody (wrongly) sets this slave to be a slave of itself
|
|
|
|
without using --replicate-same-server-id (an unsupported
|
|
|
|
configuration which does nothing), then group_master_log_pos
|
|
|
|
will grow and group_master_log_name will stay "".
|
|
|
|
*/
|
|
|
|
if (*group_master_log_name)
|
|
|
|
{
|
|
|
|
char *basename= (group_master_log_name +
|
|
|
|
dirname_length(group_master_log_name));
|
|
|
|
/*
|
|
|
|
First compare the parts before the extension.
|
|
|
|
Find the dot in the master's log basename,
|
|
|
|
and protect against user's input error :
|
|
|
|
if the names do not match up to '.' included, return error
|
|
|
|
*/
|
|
|
|
char *q= (char*)(fn_ext(basename)+1);
|
|
|
|
if (strncmp(basename, log_name_tmp, (int)(q-basename)))
|
|
|
|
{
|
|
|
|
error= -2;
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
// Now compare extensions.
|
|
|
|
char *q_end;
|
|
|
|
ulong group_master_log_name_extension= strtoul(q, &q_end, 10);
|
|
|
|
if (group_master_log_name_extension < log_name_extension)
|
|
|
|
cmp_result= -1 ;
|
|
|
|
else
|
|
|
|
cmp_result= (group_master_log_name_extension > log_name_extension) ? 1 : 0 ;
|
|
|
|
|
|
|
|
pos_reached= ((!cmp_result && group_master_log_pos >= (ulonglong)log_pos) ||
|
|
|
|
cmp_result > 0);
|
|
|
|
if (pos_reached || thd->killed)
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
|
|
|
//wait for master update, with optional timeout.
|
|
|
|
|
|
|
|
DBUG_PRINT("info",("Waiting for master update"));
|
|
|
|
/*
|
2010-01-07 06:42:07 +01:00
|
|
|
We are going to mysql_cond_(timed)wait(); if the SQL thread stops it
|
2006-10-31 12:23:14 +01:00
|
|
|
will wake us up.
|
|
|
|
*/
|
2010-10-28 16:31:21 +02:00
|
|
|
thd_wait_begin(thd, THD_WAIT_BINLOG);
|
2006-10-31 12:23:14 +01:00
|
|
|
if (timeout > 0)
|
|
|
|
{
|
|
|
|
/*
|
2010-01-07 06:42:07 +01:00
|
|
|
Note that mysql_cond_timedwait checks for the timeout
|
2006-10-31 12:23:14 +01:00
|
|
|
before for the condition ; i.e. it returns ETIMEDOUT
|
|
|
|
if the system time equals or exceeds the time specified by abstime
|
|
|
|
before the condition variable is signaled or broadcast, _or_ if
|
|
|
|
the absolute time specified by abstime has already passed at the time
|
|
|
|
of the call.
|
2010-01-07 06:42:07 +01:00
|
|
|
For that reason, mysql_cond_timedwait will do the "timeoutting" job
|
2006-10-31 12:23:14 +01:00
|
|
|
even if its condition is always immediately signaled (case of a loaded
|
|
|
|
master).
|
|
|
|
*/
|
2010-01-07 06:42:07 +01:00
|
|
|
error= mysql_cond_timedwait(&data_cond, &data_lock, &abstime);
|
2006-10-31 12:23:14 +01:00
|
|
|
}
|
|
|
|
else
|
2010-01-07 06:42:07 +01:00
|
|
|
mysql_cond_wait(&data_cond, &data_lock);
|
2010-10-28 16:31:21 +02:00
|
|
|
thd_wait_end(thd);
|
2006-10-31 12:23:14 +01:00
|
|
|
DBUG_PRINT("info",("Got signal of master update or timed out"));
|
|
|
|
if (error == ETIMEDOUT || error == ETIME)
|
|
|
|
{
|
|
|
|
error= -1;
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
error=0;
|
|
|
|
event_count++;
|
|
|
|
DBUG_PRINT("info",("Testing if killed or SQL thread not running"));
|
|
|
|
}
|
|
|
|
|
|
|
|
err:
|
fixes for test failures
and small collateral changes
mysql-test/lib/My/Test.pm:
somehow with "print" we get truncated writes sometimes
mysql-test/suite/perfschema/r/digest_table_full.result:
md5 hashes of statement digests differ, because yacc token codes are different in mariadb
mysql-test/suite/perfschema/r/dml_handler.result:
host table is not ported over yet
mysql-test/suite/perfschema/r/information_schema.result:
host table is not ported over yet
mysql-test/suite/perfschema/r/nesting.result:
this differs, because we don't rewrite general log queries, and multi-statement
packets are logged as a one entry. this result file is identical to what mysql-5.6.5
produces with the --log-raw option.
mysql-test/suite/perfschema/r/relaylog.result:
MariaDB modifies the binlog index file directly, while MySQL 5.6 has a feature "crash-safe binlog index" and modifies a special "crash-safe" shadow copy of the index file and then moves it over. That's why this test shows "NONE" index file writes in MySQL and "MANY" in MariaDB.
mysql-test/suite/perfschema/r/server_init.result:
MariaDB initializes the "manager" resources from the "manager" thread, and starts this thread only when --flush-time is not 0. MySQL 5.6 initializes "manager" resources unconditionally on server startup.
mysql-test/suite/perfschema/r/stage_mdl_global.result:
this differs, because MariaDB disables query cache when query_cache_size=0. MySQL does not
do that, and this causes useless mutex locks and waits.
mysql-test/suite/perfschema/r/statement_digest.result:
md5 hashes of statement digests differ, because yacc token codes are different in mariadb
mysql-test/suite/perfschema/r/statement_digest_consumers.result:
md5 hashes of statement digests differ, because yacc token codes are different in mariadb
mysql-test/suite/perfschema/r/statement_digest_long_query.result:
md5 hashes of statement digests differ, because yacc token codes are different in mariadb
mysql-test/suite/rpl/r/rpl_mixed_drop_create_temp_table.result:
will be updated to match 5.6 when alfranio.correia@oracle.com-20110512172919-c1b5kmum4h52g0ni and anders.song@greatopensource.com-20110105052107-zoab0bsf5a6xxk2y are merged
mysql-test/suite/rpl/r/rpl_non_direct_mixed_mixing_engines.result:
will be updated to match 5.6 when anders.song@greatopensource.com-20110105052107-zoab0bsf5a6xxk2y is merged
2012-09-27 20:09:46 +02:00
|
|
|
thd->EXIT_COND(&old_stage);
|
2006-10-31 12:23:14 +01:00
|
|
|
DBUG_PRINT("exit",("killed: %d abort: %d slave_running: %d \
|
|
|
|
improper_arguments: %d timed_out: %d",
|
|
|
|
thd->killed_errno(),
|
|
|
|
(int) (init_abort_pos_wait != abort_pos_wait),
|
|
|
|
(int) slave_running,
|
|
|
|
(int) (error == -2),
|
|
|
|
(int) (error == -1)));
|
|
|
|
if (thd->killed || init_abort_pos_wait != abort_pos_wait ||
|
|
|
|
!slave_running)
|
|
|
|
{
|
|
|
|
error= -2;
|
|
|
|
}
|
|
|
|
DBUG_RETURN( error ? error : event_count );
|
|
|
|
}
|
|
|
|
|
|
|
|
|
2007-08-16 07:37:50 +02:00
|
|
|
void Relay_log_info::inc_group_relay_log_pos(ulonglong log_pos,
|
2013-10-17 14:11:19 +02:00
|
|
|
rpl_group_info *rgi,
|
|
|
|
bool skip_lock)
|
2006-10-31 12:23:14 +01:00
|
|
|
{
|
2007-08-16 07:37:50 +02:00
|
|
|
DBUG_ENTER("Relay_log_info::inc_group_relay_log_pos");
|
2006-10-31 12:23:14 +01:00
|
|
|
|
2016-09-22 08:26:45 +02:00
|
|
|
if (skip_lock)
|
|
|
|
mysql_mutex_assert_owner(&data_lock);
|
|
|
|
else
|
2010-01-07 06:42:07 +01:00
|
|
|
mysql_mutex_lock(&data_lock);
|
2016-09-22 08:26:45 +02:00
|
|
|
|
2013-10-17 14:11:19 +02:00
|
|
|
rgi->inc_event_relay_log_pos();
|
2013-10-23 15:03:03 +02:00
|
|
|
DBUG_PRINT("info", ("log_pos: %lu group_master_log_pos: %lu",
|
|
|
|
(long) log_pos, (long) group_master_log_pos));
|
|
|
|
if (rgi->is_parallel_exec)
|
2013-10-17 14:11:19 +02:00
|
|
|
{
|
|
|
|
/* In case of parallel replication, do not update the position backwards. */
|
MDEV-7237: Parallel replication: incorrect relaylog position after stop/start the slave
The replication relay log position was sometimes updated incorrectly at the
end of a transaction in parallel replication. This happened because the relay
log file name was taken from the current Relay_log_info (SQL driver thread),
not the correct value for the transaction in question.
The result was that if a transaction was applied while the SQL driver thread
was at least one relay log file ahead, _and_ the SQL thread was subsequently
stopped before applying any events from the most recent relay log file, then
the relay log position would be incorrect - wrong relay log file name. Thus,
when the slave was started again, usually a relay log read error would result,
or in rare cases, if the position happened to be readable, the slave might
even skip arbitrary amounts of events.
In GTID mode, the relay log position is reset when both slave threads are
restarted, so this bug would only be seen in non-GTID mode, or in GTID mode
when only the SQL thread, not the IO thread, was stopped.
2014-12-01 13:53:57 +01:00
|
|
|
int cmp= strcmp(group_relay_log_name, rgi->event_relay_log_name);
|
2013-10-17 14:11:19 +02:00
|
|
|
if (cmp < 0)
|
|
|
|
{
|
2013-12-17 10:50:34 +01:00
|
|
|
group_relay_log_pos= rgi->future_event_relay_log_pos;
|
MDEV-7237: Parallel replication: incorrect relaylog position after stop/start the slave
The replication relay log position was sometimes updated incorrectly at the
end of a transaction in parallel replication. This happened because the relay
log file name was taken from the current Relay_log_info (SQL driver thread),
not the correct value for the transaction in question.
The result was that if a transaction was applied while the SQL driver thread
was at least one relay log file ahead, _and_ the SQL thread was subsequently
stopped before applying any events from the most recent relay log file, then
the relay log position would be incorrect - wrong relay log file name. Thus,
when the slave was started again, usually a relay log read error would result,
or in rare cases, if the position happened to be readable, the slave might
even skip arbitrary amounts of events.
In GTID mode, the relay log position is reset when both slave threads are
restarted, so this bug would only be seen in non-GTID mode, or in GTID mode
when only the SQL thread, not the IO thread, was stopped.
2014-12-01 13:53:57 +01:00
|
|
|
strmake_buf(group_relay_log_name, rgi->event_relay_log_name);
|
2013-10-17 14:11:19 +02:00
|
|
|
notify_group_relay_log_name_update();
|
2013-12-17 10:50:34 +01:00
|
|
|
} else if (cmp == 0 && group_relay_log_pos < rgi->future_event_relay_log_pos)
|
|
|
|
group_relay_log_pos= rgi->future_event_relay_log_pos;
|
2006-10-31 12:23:14 +01:00
|
|
|
|
2013-10-24 08:53:48 +02:00
|
|
|
/*
|
|
|
|
In the parallel case we need to update the master_log_name here, rather
|
|
|
|
than in Rotate_log_event::do_update_pos().
|
|
|
|
*/
|
2013-10-23 15:03:03 +02:00
|
|
|
cmp= strcmp(group_master_log_name, rgi->future_event_master_log_name);
|
|
|
|
if (cmp <= 0)
|
|
|
|
{
|
|
|
|
if (cmp < 0)
|
|
|
|
{
|
|
|
|
strcpy(group_master_log_name, rgi->future_event_master_log_name);
|
2013-10-30 07:52:30 +01:00
|
|
|
group_master_log_pos= log_pos;
|
2013-10-23 15:03:03 +02:00
|
|
|
}
|
2013-10-30 07:52:30 +01:00
|
|
|
else if (group_master_log_pos < log_pos)
|
2013-10-23 15:03:03 +02:00
|
|
|
group_master_log_pos= log_pos;
|
|
|
|
}
|
2015-10-22 10:28:51 +02:00
|
|
|
|
|
|
|
/*
|
|
|
|
In the parallel case, we only update the Seconds_Behind_Master at the
|
|
|
|
end of a transaction. In the non-parallel case, the value is updated as
|
|
|
|
soon as an event is read from the relay log; however this would be too
|
|
|
|
confusing for the user, seeing the slave reported as up-to-date when
|
|
|
|
potentially thousands of events are still queued up for worker threads
|
|
|
|
waiting for execution.
|
|
|
|
*/
|
|
|
|
if (rgi->last_master_timestamp &&
|
|
|
|
rgi->last_master_timestamp > last_master_timestamp)
|
|
|
|
last_master_timestamp= rgi->last_master_timestamp;
|
2013-10-17 14:11:19 +02:00
|
|
|
}
|
|
|
|
else
|
|
|
|
{
|
|
|
|
/* Non-parallel case. */
|
|
|
|
group_relay_log_pos= event_relay_log_pos;
|
|
|
|
strmake_buf(group_relay_log_name, event_relay_log_name);
|
|
|
|
notify_group_relay_log_name_update();
|
2015-08-31 16:23:01 +02:00
|
|
|
if (log_pos) // not 3.23 binlogs (no log_pos there) and not Stop_log_event
|
2013-10-23 15:03:03 +02:00
|
|
|
group_master_log_pos= log_pos;
|
2013-10-17 14:11:19 +02:00
|
|
|
}
|
2006-10-31 12:23:14 +01:00
|
|
|
|
|
|
|
/*
|
|
|
|
If the slave does not support transactions and replicates a transaction,
|
|
|
|
users should not trust group_master_log_pos (which they can display with
|
|
|
|
SHOW SLAVE STATUS or read from relay-log.info), because to compute
|
|
|
|
group_master_log_pos the slave relies on log_pos stored in the master's
|
|
|
|
binlog, but if we are in a master's transaction these positions are always
|
|
|
|
the BEGIN's one (excepted for the COMMIT), so group_master_log_pos does
|
|
|
|
not advance as it should on the non-transactional slave (it advances by
|
|
|
|
big leaps, whereas it should advance by small leaps).
|
|
|
|
*/
|
|
|
|
/*
|
|
|
|
In 4.x we used the event's len to compute the positions here. This is
|
|
|
|
wrong if the event was 3.23/4.0 and has been converted to 5.0, because
|
|
|
|
then the event's len is not what is was in the master's binlog, so this
|
|
|
|
will make a wrong group_master_log_pos (yes it's a bug in 3.23->4.0
|
|
|
|
replication: Exec_master_log_pos is wrong). Only way to solve this is to
|
|
|
|
have the original offset of the end of the event the relay log. This is
|
|
|
|
what we do in 5.0: log_pos has become "end_log_pos" (because the real use
|
|
|
|
of log_pos in 4.0 was to compute the end_log_pos; so better to store
|
|
|
|
end_log_pos instead of begin_log_pos.
|
|
|
|
If we had not done this fix here, the problem would also have appeared
|
|
|
|
when the slave and master are 5.0 but with different event length (for
|
|
|
|
example the slave is more recent than the master and features the event
|
|
|
|
UID). It would give false MASTER_POS_WAIT, false Exec_master_log_pos in
|
|
|
|
SHOW SLAVE STATUS, and so the user would do some CHANGE MASTER using this
|
|
|
|
value which would lead to badly broken replication.
|
|
|
|
Even the relay_log_pos will be corrupted in this case, because the len is
|
|
|
|
the relay log is not "val".
|
|
|
|
With the end_log_pos solution, we avoid computations involving lengthes.
|
|
|
|
*/
|
2010-01-07 06:42:07 +01:00
|
|
|
mysql_cond_broadcast(&data_cond);
|
2006-10-31 12:23:14 +01:00
|
|
|
if (!skip_lock)
|
2010-01-07 06:42:07 +01:00
|
|
|
mysql_mutex_unlock(&data_lock);
|
2006-10-31 12:23:14 +01:00
|
|
|
DBUG_VOID_RETURN;
|
|
|
|
}
|
|
|
|
|
|
|
|
|
2007-08-16 07:37:50 +02:00
|
|
|
void Relay_log_info::close_temporary_tables()
|
2006-10-31 12:23:14 +01:00
|
|
|
{
|
2007-08-16 07:37:50 +02:00
|
|
|
DBUG_ENTER("Relay_log_info::close_temporary_tables");
|
2006-10-31 12:23:14 +01:00
|
|
|
|
2016-06-10 22:19:59 +02:00
|
|
|
TMP_TABLE_SHARE *share;
|
|
|
|
TABLE *table;
|
|
|
|
|
|
|
|
if (!save_temporary_tables)
|
2006-10-31 12:23:14 +01:00
|
|
|
{
|
2016-06-10 22:19:59 +02:00
|
|
|
/* There are no temporary tables. */
|
|
|
|
DBUG_VOID_RETURN;
|
|
|
|
}
|
|
|
|
|
|
|
|
while ((share= save_temporary_tables->pop_front()))
|
|
|
|
{
|
|
|
|
/*
|
|
|
|
Iterate over the list of tables for this TABLE_SHARE and close them.
|
|
|
|
*/
|
|
|
|
while ((table= share->all_tmp_tables.pop_front()))
|
|
|
|
{
|
|
|
|
DBUG_PRINT("tmptable", ("closing table: '%s'.'%s'",
|
|
|
|
table->s->db.str, table->s->table_name.str));
|
|
|
|
|
|
|
|
/* Reset in_use as the table may have been created by another thd */
|
|
|
|
table->in_use= 0;
|
|
|
|
/*
|
|
|
|
Lets not free TABLE_SHARE here as there could be multiple TABLEs opened
|
|
|
|
for the same table (TABLE_SHARE).
|
|
|
|
*/
|
|
|
|
closefrm(table);
|
|
|
|
my_free(table);
|
|
|
|
}
|
Fixes for parallel slave:
- Made slaves temporary table multi-thread slave safe by adding mutex around save_temporary_table usage.
- rli->save_temporary_tables is the active list of all used temporary tables
- This is copied to THD->temporary_tables when temporary tables are opened and updated when temporary tables are closed
- Added THD->lock_temporary_tables() and THD->unlock_temporary_tables() to simplify this.
- Relay_log_info->sql_thd renamed to Relay_log_info->sql_driver_thd to avoid wrong usage for merged code.
- Added is_part_of_group() to mark functions that are part of the next function. This replaces setting IN_STMT when events are executed.
- Added is_begin(), is_commit() and is_rollback() functions to Query_log_event to simplify code.
- If slave_skip_counter is set run things in single threaded mode. This simplifies code for skipping events.
- Updating state of relay log (IN_STMT and IN_TRANSACTION) is moved to one single function: update_state_of_relay_log()
We can't use OPTION_BEGIN to check for the state anymore as the sql_driver and sql execution threads may be different.
Clear IN_STMT and IN_TRANSACTION in init_relay_log_pos() and Relay_log_info::cleanup_context() to ensure the flags doesn't survive slave restarts
is_in_group() is now independent of state of executed transaction.
- Reset thd->transaction.all.modified_non_trans_table() if we did set it for single table row events.
This was mainly for keeping the flag as documented.
- Changed slave_open_temp_tables to uint32 to be able to use atomic operators on it.
- Relay_log_info::sleep_lock -> rpl_group_info::sleep_lock
- Relay_log_info::sleep_cond -> rpl_group_info::sleep_cond
- Changed some functions to take rpl_group_info instead of Relay_log_info to make them multi-slave safe and to simplify usage
- do_shall_skip()
- continue_group()
- sql_slave_killed()
- next_event()
- Simplifed arguments to io_salve_killed(), check_io_slave_killed() and sql_slave_killed(); No reason to supply THD as this is part of the given structure.
- set_thd_in_use_temporary_tables() removed as in_use is set on usage
- Added information to thd_proc_info() which thread is waiting for slave mutex to exit.
- In open_table() reuse code from find_temporary_table()
Other things:
- More DBUG statements
- Fixed the rpl_incident.test can be run with --debug
- More comments
- Disabled not used function rpl_connect_master()
mysql-test/suite/perfschema/r/all_instances.result:
Moved sleep_lock and sleep_cond to rpl_group_info
mysql-test/suite/rpl/r/rpl_incident.result:
Updated result
mysql-test/suite/rpl/t/rpl_incident-master.opt:
Not needed anymore
mysql-test/suite/rpl/t/rpl_incident.test:
Fixed that test can be run with --debug
sql/handler.cc:
More DBUG_PRINT
sql/log.cc:
More comments
sql/log_event.cc:
Added DBUG statements
do_shall_skip(), continue_group() now takes rpl_group_info param
Use is_begin(), is_commit() and is_rollback() functions instead of inspecting query string
We don't have set slaves temporary tables 'in_use' as this is now done when tables are opened.
Removed IN_STMT flag setting. This is now done in update_state_of_relay_log()
Use IN_TRANSACTION flag to test state of relay log.
In rows_event_stmt_cleanup() reset thd->transaction.all.modified_non_trans_table if we had set this before.
sql/log_event.h:
do_shall_skip(), continue_group() now takes rpl_group_info param
Added is_part_of_group() to mark events that are part of the next event. This replaces setting IN_STMT when events are executed.
Added is_begin(), is_commit() and is_rollback() functions to Query_log_event to simplify code.
sql/log_event_old.cc:
Removed IN_STMT flag setting. This is now done in update_state_of_relay_log()
do_shall_skip(), continue_group() now takes rpl_group_info param
sql/log_event_old.h:
Added is_part_of_group() to mark events that are part of the next event.
do_shall_skip(), continue_group() now takes rpl_group_info param
sql/mysqld.cc:
Changed slave_open_temp_tables to uint32 to be able to use atomic operators on it.
Relay_log_info::sleep_lock -> Rpl_group_info::sleep_lock
Relay_log_info::sleep_cond -> Rpl_group_info::sleep_cond
sql/mysqld.h:
Updated types and names
sql/rpl_gtid.cc:
More DBUG
sql/rpl_parallel.cc:
Updated TODO section
Set thd for event that is execution
Use new is_begin(), is_commit() and is_rollback() functions.
More comments
sql/rpl_rli.cc:
sql_thd -> sql_driver_thd
Relay_log_info::sleep_lock -> rpl_group_info::sleep_lock
Relay_log_info::sleep_cond -> rpl_group_info::sleep_cond
Clear IN_STMT and IN_TRANSACTION in init_relay_log_pos() and Relay_log_info::cleanup_context() to ensure the flags doesn't survive slave restarts.
Reset table->in_use for temporary tables as the table may have been used by another THD.
Use IN_TRANSACTION instead of OPTION_BEGIN to check state of relay log.
Removed IN_STMT flag setting. This is now done in update_state_of_relay_log()
sql/rpl_rli.h:
Changed relay log state flags to bit masks instead of bit positions (most other code we have uses bit masks)
Added IN_TRANSACTION to mark if we are in a BEGIN ... COMMIT section.
save_temporary_tables is now thread safe
Relay_log_info::sleep_lock -> rpl_group_info::sleep_lock
Relay_log_info::sleep_cond -> rpl_group_info::sleep_cond
Relay_log_info->sql_thd renamed to Relay_log_info->sql_driver_thd to avoid wrong usage for merged code
is_in_group() is now independent of state of executed transaction.
sql/slave.cc:
Simplifed arguments to io_salve_killed(), sql_slave_killed() and check_io_slave_killed(); No reason to supply THD as this is part of the given structure.
set_thd_in_use_temporary_tables() removed as in_use is set on usage in sql_base.cc
sql_thd -> sql_driver_thd
More DBUG
Added update_state_of_relay_log() which will calculate the IN_STMT and IN_TRANSACTION state of the relay log after the current element is executed.
If slave_skip_counter is set run things in single threaded mode.
Simplifed arguments to io_salve_killed(), check_io_slave_killed() and sql_slave_killed(); No reason to supply THD as this is part of the given structure.
Added information to thd_proc_info() which thread is waiting for slave mutex to exit.
Disabled not used function rpl_connect_master()
Updated argument to next_event()
sql/sql_base.cc:
Added mutex around usage of slave's temporary tables. The active list is always kept up to date in sql->rgi_slave->save_temporary_tables.
Clear thd->temporary_tables after query (safety)
More DBUG
When using temporary table, set table->in_use to current thd as the THD may be different for slave threads.
Some code is ifdef:ed with REMOVE_AFTER_MERGE_WITH_10 as the given code in 10.0 is not yet in this tree.
In open_table() reuse code from find_temporary_table()
sql/sql_binlog.cc:
rli->sql_thd -> rli->sql_driver_thd
Remove duplicate setting of rgi->rli
sql/sql_class.cc:
Added helper functions rgi_lock_temporary_tables() and rgi_unlock_temporary_tables()
Would have been nicer to have these inline, but there was no easy way to do that
sql/sql_class.h:
Added functions to protect slaves temporary tables
sql/sql_parse.cc:
Added DBUG_PRINT
sql/transaction.cc:
Added comment
2013-10-13 23:24:05 +02:00
|
|
|
|
2006-10-31 12:23:14 +01:00
|
|
|
/*
|
|
|
|
Don't ask for disk deletion. For now, anyway they will be deleted when
|
|
|
|
slave restarts, but it is a better intention to not delete them.
|
|
|
|
*/
|
2016-06-10 22:19:59 +02:00
|
|
|
|
|
|
|
free_table_share(share);
|
|
|
|
my_free(share);
|
2006-10-31 12:23:14 +01:00
|
|
|
}
|
2016-06-10 22:19:59 +02:00
|
|
|
|
|
|
|
/* By now, there mustn't be any elements left in the list. */
|
|
|
|
DBUG_ASSERT(save_temporary_tables->is_empty());
|
|
|
|
|
|
|
|
my_free(save_temporary_tables);
|
|
|
|
save_temporary_tables= NULL;
|
2006-10-31 12:23:14 +01:00
|
|
|
slave_open_temp_tables= 0;
|
2016-06-10 22:19:59 +02:00
|
|
|
|
2006-10-31 12:23:14 +01:00
|
|
|
DBUG_VOID_RETURN;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
purge_relay_logs()
|
|
|
|
|
2015-07-15 15:27:14 +02:00
|
|
|
@param rli Relay log information
|
|
|
|
@param thd thread id. May be zero during startup
|
|
|
|
|
2006-10-31 12:23:14 +01:00
|
|
|
NOTES
|
|
|
|
Assumes to have a run lock on rli and that no slave thread are running.
|
|
|
|
*/
|
|
|
|
|
2007-08-16 07:37:50 +02:00
|
|
|
int purge_relay_logs(Relay_log_info* rli, THD *thd, bool just_reset,
|
2006-10-31 12:23:14 +01:00
|
|
|
const char** errmsg)
|
|
|
|
{
|
|
|
|
int error=0;
|
2017-02-28 05:30:51 +01:00
|
|
|
const char *ln;
|
|
|
|
char name_buf[FN_REFLEN];
|
2006-10-31 12:23:14 +01:00
|
|
|
DBUG_ENTER("purge_relay_logs");
|
|
|
|
|
|
|
|
/*
|
|
|
|
Even if rli->inited==0, we still try to empty rli->master_log_* variables.
|
|
|
|
Indeed, rli->inited==0 does not imply that they already are empty.
|
|
|
|
It could be that slave's info initialization partly succeeded :
|
|
|
|
for example if relay-log.info existed but *relay-bin*.*
|
2016-09-22 13:36:45 +02:00
|
|
|
have been manually removed, Relay_log_info::init() reads the old
|
|
|
|
relay-log.info and fills rli->master_log_*, then Relay_log_info::init()
|
2006-10-31 12:23:14 +01:00
|
|
|
checks for the existence of the relay log, this fails and
|
2016-09-22 13:36:45 +02:00
|
|
|
Relay_log_info::init() leaves rli->inited to 0.
|
2006-10-31 12:23:14 +01:00
|
|
|
In that pathological case, rli->master_log_pos* will be properly reinited
|
|
|
|
at the next START SLAVE (as RESET SLAVE or CHANGE
|
|
|
|
MASTER, the callers of purge_relay_logs, will delete bogus *.info files
|
|
|
|
or replace them with correct files), however if the user does SHOW SLAVE
|
|
|
|
STATUS before START SLAVE, he will see old, confusing rli->master_log_*.
|
|
|
|
In other words, we reinit rli->master_log_* for SHOW SLAVE STATUS
|
|
|
|
to display fine in any case.
|
|
|
|
*/
|
|
|
|
|
|
|
|
rli->group_master_log_name[0]= 0;
|
|
|
|
rli->group_master_log_pos= 0;
|
|
|
|
|
|
|
|
if (!rli->inited)
|
|
|
|
{
|
|
|
|
DBUG_PRINT("info", ("rli->inited == 0"));
|
2017-02-28 05:30:51 +01:00
|
|
|
if (rli->error_on_rli_init_info)
|
|
|
|
{
|
|
|
|
ln= rli->relay_log.generate_name(opt_relay_logname, "-relay-bin",
|
|
|
|
1, name_buf);
|
2006-10-31 12:23:14 +01:00
|
|
|
|
2017-02-28 05:30:51 +01:00
|
|
|
if (rli->relay_log.open_index_file(opt_relaylog_index_name, ln, TRUE))
|
|
|
|
{
|
|
|
|
sql_print_error("Unable to purge relay log files. Failed to open relay "
|
|
|
|
"log index file:%s.", rli->relay_log.get_index_fname());
|
|
|
|
DBUG_RETURN(1);
|
|
|
|
}
|
2017-07-27 12:43:45 +02:00
|
|
|
mysql_mutex_lock(rli->relay_log.get_log_lock());
|
2017-08-08 10:18:43 +02:00
|
|
|
if (rli->relay_log.open(ln, LOG_BIN, 0, 0, SEQ_READ_APPEND,
|
2017-09-28 12:38:02 +02:00
|
|
|
(ulong)(rli->max_relay_log_size ? rli->max_relay_log_size :
|
2017-02-28 05:30:51 +01:00
|
|
|
max_binlog_size), 1, TRUE))
|
|
|
|
{
|
|
|
|
sql_print_error("Unable to purge relay log files. Failed to open relay "
|
|
|
|
"log file:%s.", rli->relay_log.get_log_fname());
|
2017-07-27 12:43:45 +02:00
|
|
|
mysql_mutex_unlock(rli->relay_log.get_log_lock());
|
2017-02-28 05:30:51 +01:00
|
|
|
DBUG_RETURN(1);
|
|
|
|
}
|
2017-07-27 12:43:45 +02:00
|
|
|
mysql_mutex_unlock(rli->relay_log.get_log_lock());
|
2017-02-28 05:30:51 +01:00
|
|
|
}
|
|
|
|
else
|
|
|
|
DBUG_RETURN(0);
|
|
|
|
}
|
|
|
|
else
|
|
|
|
{
|
|
|
|
DBUG_ASSERT(rli->slave_running == 0);
|
|
|
|
DBUG_ASSERT(rli->mi->slave_running == 0);
|
|
|
|
}
|
2010-01-07 06:42:07 +01:00
|
|
|
mysql_mutex_lock(&rli->data_lock);
|
2006-10-31 12:23:14 +01:00
|
|
|
|
|
|
|
/*
|
|
|
|
we close the relay log fd possibly left open by the slave SQL thread,
|
|
|
|
to be able to delete it; the relay log fd possibly left open by the slave
|
|
|
|
I/O thread will be closed naturally in reset_logs() by the
|
|
|
|
close(LOG_CLOSE_TO_BE_OPENED) call
|
|
|
|
*/
|
|
|
|
if (rli->cur_log_fd >= 0)
|
|
|
|
{
|
|
|
|
end_io_cache(&rli->cache_buf);
|
2010-01-07 06:42:07 +01:00
|
|
|
mysql_file_close(rli->cur_log_fd, MYF(MY_WME));
|
2006-10-31 12:23:14 +01:00
|
|
|
rli->cur_log_fd= -1;
|
|
|
|
}
|
|
|
|
|
2015-07-15 15:27:14 +02:00
|
|
|
if (rli->relay_log.reset_logs(thd, !just_reset, NULL, 0, 0))
|
2006-10-31 12:23:14 +01:00
|
|
|
{
|
|
|
|
*errmsg = "Failed during log reset";
|
|
|
|
error=1;
|
|
|
|
goto err;
|
|
|
|
}
|
Fix error handling for GTID and domain-based parallel replication
This occurs when replication stops with an error, domain-based parallel
replication is used, and the GTID position contains more than one domain.
Furthermore, it relates to the case where the SQL thread is restarted
without first stopping the IO thread.
In this case, the file/offset relay-log position does not correctly
represent the slave's multi-dimensional position, because other domains may
be far ahead of, or behind, the domain with the failing event. So the code
reverts the relay log position back to the start of a relay log file that is
known to be before all active domains.
There was a bug that when the SQL thread was restarted, the
rli->relay_log_state was incorrectly initialised from @@gtid_slave_pos. This
position will likely be too far ahead, due to reverting the relay log
position. Thus, if the replication fails again after the SQL thread restart,
the rli->restart_gtid_pos might be updated incorrectly. This in turn would
cause a second SQL thread restart to replicate from the wrong position, if
the IO thread was still left running.
The fix is to initialise rli->relay_log_state from @@gtid_slave_pos only
when we actually purge and re-fetch relay logs from the master, not at every
SQL thread start.
A related problem is the use of sql_slave_skip_counter to resolve
replication failures in this kind of scenario. Since the slave position is
multi-dimensional, sql_slave_skip_counter can not work properly - it is
indeterminate exactly which event is to be skipped, and is unlikely to work
as expected for the user. So make this an error in the case where
domain-based parallel replication is used with multiple domains, suggesting
instead the user to set @@gtid_slave_pos to reliably skip the desired event.
2016-01-15 12:42:51 +01:00
|
|
|
rli->relay_log_state.load(rpl_global_gtid_slave_state);
|
2006-10-31 12:23:14 +01:00
|
|
|
if (!just_reset)
|
2012-09-28 20:22:24 +02:00
|
|
|
{
|
|
|
|
/* Save name of used relay log file */
|
2013-06-06 17:51:28 +02:00
|
|
|
strmake_buf(rli->group_relay_log_name, rli->relay_log.get_log_fname());
|
|
|
|
strmake_buf(rli->event_relay_log_name, rli->relay_log.get_log_fname());
|
2012-09-28 20:22:24 +02:00
|
|
|
rli->group_relay_log_pos= rli->event_relay_log_pos= BIN_LOG_HEADER_SIZE;
|
|
|
|
rli->log_space_total= 0;
|
|
|
|
|
|
|
|
if (count_relay_log_space(rli))
|
|
|
|
{
|
|
|
|
*errmsg= "Error counting relay log space";
|
|
|
|
error=1;
|
|
|
|
goto err;
|
|
|
|
}
|
2006-10-31 12:23:14 +01:00
|
|
|
error= init_relay_log_pos(rli, rli->group_relay_log_name,
|
|
|
|
rli->group_relay_log_pos,
|
|
|
|
0 /* do not need data lock */, errmsg, 0);
|
2012-09-28 20:22:24 +02:00
|
|
|
}
|
|
|
|
else
|
|
|
|
{
|
|
|
|
/* Ensure relay log names are not used */
|
|
|
|
rli->group_relay_log_name[0]= rli->event_relay_log_name[0]= 0;
|
|
|
|
}
|
2006-10-31 12:23:14 +01:00
|
|
|
|
2017-02-28 05:30:51 +01:00
|
|
|
if (!rli->inited && rli->error_on_rli_init_info)
|
2017-07-27 12:43:45 +02:00
|
|
|
{
|
|
|
|
mysql_mutex_lock(rli->relay_log.get_log_lock());
|
2017-02-28 05:30:51 +01:00
|
|
|
rli->relay_log.close(LOG_CLOSE_INDEX | LOG_CLOSE_STOP_EVENT);
|
2017-07-27 12:43:45 +02:00
|
|
|
mysql_mutex_unlock(rli->relay_log.get_log_lock());
|
|
|
|
}
|
2006-10-31 12:23:14 +01:00
|
|
|
err:
|
2015-08-25 17:29:58 +02:00
|
|
|
DBUG_PRINT("info",("log_space_total: %llu",rli->log_space_total));
|
2010-01-07 06:42:07 +01:00
|
|
|
mysql_mutex_unlock(&rli->data_lock);
|
2006-10-31 12:23:14 +01:00
|
|
|
DBUG_RETURN(error);
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
Check if condition stated in UNTIL clause of START SLAVE is reached.
|
|
|
|
SYNOPSYS
|
2007-08-16 07:37:50 +02:00
|
|
|
Relay_log_info::is_until_satisfied()
|
2008-02-27 18:46:06 +01:00
|
|
|
master_beg_pos position of the beginning of to be executed event
|
|
|
|
(not log_pos member of the event that points to the
|
|
|
|
beginning of the following event)
|
|
|
|
|
|
|
|
|
2006-10-31 12:23:14 +01:00
|
|
|
DESCRIPTION
|
|
|
|
Checks if UNTIL condition is reached. Uses caching result of last
|
|
|
|
comparison of current log file name and target log file name. So cached
|
|
|
|
value should be invalidated if current log file name changes
|
2007-08-16 07:37:50 +02:00
|
|
|
(see Relay_log_info::notify_... functions).
|
2006-10-31 12:23:14 +01:00
|
|
|
|
|
|
|
This caching is needed to avoid of expensive string comparisons and
|
|
|
|
strtol() conversions needed for log names comparison. We don't need to
|
|
|
|
compare them each time this function is called, we only need to do this
|
|
|
|
when current log name changes. If we have UNTIL_MASTER_POS condition we
|
2007-03-30 15:29:30 +02:00
|
|
|
need to do this only after Rotate_log_event::do_apply_event() (which is
|
2006-10-31 12:23:14 +01:00
|
|
|
rare, so caching gives real benifit), and if we have UNTIL_RELAY_POS
|
|
|
|
condition then we should invalidate cached comarison value after
|
|
|
|
inc_group_relay_log_pos() which called for each group of events (so we
|
|
|
|
have some benefit if we have something like queries that use
|
|
|
|
autoincrement or if we have transactions).
|
|
|
|
|
|
|
|
Should be called ONLY if until_condition != UNTIL_NONE !
|
|
|
|
RETURN VALUE
|
|
|
|
true - condition met or error happened (condition seems to have
|
|
|
|
bad log file name)
|
|
|
|
false - condition not met
|
|
|
|
*/
|
|
|
|
|
2015-08-28 02:34:03 +02:00
|
|
|
bool Relay_log_info::is_until_satisfied(my_off_t master_beg_pos)
|
2006-10-31 12:23:14 +01:00
|
|
|
{
|
|
|
|
const char *log_name;
|
|
|
|
ulonglong log_pos;
|
2007-08-16 07:37:50 +02:00
|
|
|
DBUG_ENTER("Relay_log_info::is_until_satisfied");
|
2006-10-31 12:23:14 +01:00
|
|
|
|
|
|
|
if (until_condition == UNTIL_MASTER_POS)
|
|
|
|
{
|
2016-12-11 09:53:42 +01:00
|
|
|
log_name= (mi->using_parallel() ? future_event_master_log_name
|
|
|
|
: group_master_log_name);
|
2015-08-28 02:34:03 +02:00
|
|
|
log_pos= master_beg_pos;
|
2006-10-31 12:23:14 +01:00
|
|
|
}
|
|
|
|
else
|
2015-08-28 02:34:03 +02:00
|
|
|
{
|
|
|
|
DBUG_ASSERT(until_condition == UNTIL_RELAY_POS);
|
2006-10-31 12:23:14 +01:00
|
|
|
log_name= group_relay_log_name;
|
|
|
|
log_pos= group_relay_log_pos;
|
|
|
|
}
|
|
|
|
|
2015-08-25 17:29:58 +02:00
|
|
|
DBUG_PRINT("info", ("group_master_log_name='%s', group_master_log_pos=%llu",
|
|
|
|
group_master_log_name, group_master_log_pos));
|
|
|
|
DBUG_PRINT("info", ("group_relay_log_name='%s', group_relay_log_pos=%llu",
|
|
|
|
group_relay_log_name, group_relay_log_pos));
|
|
|
|
DBUG_PRINT("info", ("(%s) log_name='%s', log_pos=%llu",
|
|
|
|
until_condition == UNTIL_MASTER_POS ? "master" : "relay",
|
|
|
|
log_name, log_pos));
|
|
|
|
DBUG_PRINT("info", ("(%s) until_log_name='%s', until_log_pos=%llu",
|
|
|
|
until_condition == UNTIL_MASTER_POS ? "master" : "relay",
|
|
|
|
until_log_name, until_log_pos));
|
2007-01-17 15:06:37 +01:00
|
|
|
|
2006-10-31 12:23:14 +01:00
|
|
|
if (until_log_names_cmp_result == UNTIL_LOG_NAMES_CMP_UNKNOWN)
|
|
|
|
{
|
|
|
|
/*
|
|
|
|
We have no cached comparison results so we should compare log names
|
|
|
|
and cache result.
|
|
|
|
If we are after RESET SLAVE, and the SQL slave thread has not processed
|
|
|
|
any event yet, it could be that group_master_log_name is "". In that case,
|
|
|
|
just wait for more events (as there is no sensible comparison to do).
|
|
|
|
*/
|
|
|
|
|
|
|
|
if (*log_name)
|
|
|
|
{
|
|
|
|
const char *basename= log_name + dirname_length(log_name);
|
|
|
|
|
|
|
|
const char *q= (const char*)(fn_ext(basename)+1);
|
|
|
|
if (strncmp(basename, until_log_name, (int)(q-basename)) == 0)
|
|
|
|
{
|
|
|
|
/* Now compare extensions. */
|
|
|
|
char *q_end;
|
|
|
|
ulong log_name_extension= strtoul(q, &q_end, 10);
|
|
|
|
if (log_name_extension < until_log_name_extension)
|
|
|
|
until_log_names_cmp_result= UNTIL_LOG_NAMES_CMP_LESS;
|
|
|
|
else
|
|
|
|
until_log_names_cmp_result=
|
|
|
|
(log_name_extension > until_log_name_extension) ?
|
|
|
|
UNTIL_LOG_NAMES_CMP_GREATER : UNTIL_LOG_NAMES_CMP_EQUAL ;
|
|
|
|
}
|
|
|
|
else
|
|
|
|
{
|
|
|
|
/* Probably error so we aborting */
|
|
|
|
sql_print_error("Slave SQL thread is stopped because UNTIL "
|
|
|
|
"condition is bad.");
|
|
|
|
DBUG_RETURN(TRUE);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
else
|
|
|
|
DBUG_RETURN(until_log_pos == 0);
|
|
|
|
}
|
|
|
|
|
|
|
|
DBUG_RETURN(((until_log_names_cmp_result == UNTIL_LOG_NAMES_CMP_EQUAL &&
|
|
|
|
log_pos >= until_log_pos) ||
|
|
|
|
until_log_names_cmp_result == UNTIL_LOG_NAMES_CMP_GREATER));
|
|
|
|
}
|
|
|
|
|
|
|
|
|
2017-02-05 01:23:49 +01:00
|
|
|
bool Relay_log_info::stmt_done(my_off_t event_master_log_pos, THD *thd,
|
2013-09-13 15:09:57 +02:00
|
|
|
rpl_group_info *rgi)
|
2007-04-12 08:58:04 +02:00
|
|
|
{
|
2017-02-05 01:23:49 +01:00
|
|
|
int error= 0;
|
Fixes for parallel slave:
- Made slaves temporary table multi-thread slave safe by adding mutex around save_temporary_table usage.
- rli->save_temporary_tables is the active list of all used temporary tables
- This is copied to THD->temporary_tables when temporary tables are opened and updated when temporary tables are closed
- Added THD->lock_temporary_tables() and THD->unlock_temporary_tables() to simplify this.
- Relay_log_info->sql_thd renamed to Relay_log_info->sql_driver_thd to avoid wrong usage for merged code.
- Added is_part_of_group() to mark functions that are part of the next function. This replaces setting IN_STMT when events are executed.
- Added is_begin(), is_commit() and is_rollback() functions to Query_log_event to simplify code.
- If slave_skip_counter is set run things in single threaded mode. This simplifies code for skipping events.
- Updating state of relay log (IN_STMT and IN_TRANSACTION) is moved to one single function: update_state_of_relay_log()
We can't use OPTION_BEGIN to check for the state anymore as the sql_driver and sql execution threads may be different.
Clear IN_STMT and IN_TRANSACTION in init_relay_log_pos() and Relay_log_info::cleanup_context() to ensure the flags doesn't survive slave restarts
is_in_group() is now independent of state of executed transaction.
- Reset thd->transaction.all.modified_non_trans_table() if we did set it for single table row events.
This was mainly for keeping the flag as documented.
- Changed slave_open_temp_tables to uint32 to be able to use atomic operators on it.
- Relay_log_info::sleep_lock -> rpl_group_info::sleep_lock
- Relay_log_info::sleep_cond -> rpl_group_info::sleep_cond
- Changed some functions to take rpl_group_info instead of Relay_log_info to make them multi-slave safe and to simplify usage
- do_shall_skip()
- continue_group()
- sql_slave_killed()
- next_event()
- Simplifed arguments to io_salve_killed(), check_io_slave_killed() and sql_slave_killed(); No reason to supply THD as this is part of the given structure.
- set_thd_in_use_temporary_tables() removed as in_use is set on usage
- Added information to thd_proc_info() which thread is waiting for slave mutex to exit.
- In open_table() reuse code from find_temporary_table()
Other things:
- More DBUG statements
- Fixed the rpl_incident.test can be run with --debug
- More comments
- Disabled not used function rpl_connect_master()
mysql-test/suite/perfschema/r/all_instances.result:
Moved sleep_lock and sleep_cond to rpl_group_info
mysql-test/suite/rpl/r/rpl_incident.result:
Updated result
mysql-test/suite/rpl/t/rpl_incident-master.opt:
Not needed anymore
mysql-test/suite/rpl/t/rpl_incident.test:
Fixed that test can be run with --debug
sql/handler.cc:
More DBUG_PRINT
sql/log.cc:
More comments
sql/log_event.cc:
Added DBUG statements
do_shall_skip(), continue_group() now takes rpl_group_info param
Use is_begin(), is_commit() and is_rollback() functions instead of inspecting query string
We don't have set slaves temporary tables 'in_use' as this is now done when tables are opened.
Removed IN_STMT flag setting. This is now done in update_state_of_relay_log()
Use IN_TRANSACTION flag to test state of relay log.
In rows_event_stmt_cleanup() reset thd->transaction.all.modified_non_trans_table if we had set this before.
sql/log_event.h:
do_shall_skip(), continue_group() now takes rpl_group_info param
Added is_part_of_group() to mark events that are part of the next event. This replaces setting IN_STMT when events are executed.
Added is_begin(), is_commit() and is_rollback() functions to Query_log_event to simplify code.
sql/log_event_old.cc:
Removed IN_STMT flag setting. This is now done in update_state_of_relay_log()
do_shall_skip(), continue_group() now takes rpl_group_info param
sql/log_event_old.h:
Added is_part_of_group() to mark events that are part of the next event.
do_shall_skip(), continue_group() now takes rpl_group_info param
sql/mysqld.cc:
Changed slave_open_temp_tables to uint32 to be able to use atomic operators on it.
Relay_log_info::sleep_lock -> Rpl_group_info::sleep_lock
Relay_log_info::sleep_cond -> Rpl_group_info::sleep_cond
sql/mysqld.h:
Updated types and names
sql/rpl_gtid.cc:
More DBUG
sql/rpl_parallel.cc:
Updated TODO section
Set thd for event that is execution
Use new is_begin(), is_commit() and is_rollback() functions.
More comments
sql/rpl_rli.cc:
sql_thd -> sql_driver_thd
Relay_log_info::sleep_lock -> rpl_group_info::sleep_lock
Relay_log_info::sleep_cond -> rpl_group_info::sleep_cond
Clear IN_STMT and IN_TRANSACTION in init_relay_log_pos() and Relay_log_info::cleanup_context() to ensure the flags doesn't survive slave restarts.
Reset table->in_use for temporary tables as the table may have been used by another THD.
Use IN_TRANSACTION instead of OPTION_BEGIN to check state of relay log.
Removed IN_STMT flag setting. This is now done in update_state_of_relay_log()
sql/rpl_rli.h:
Changed relay log state flags to bit masks instead of bit positions (most other code we have uses bit masks)
Added IN_TRANSACTION to mark if we are in a BEGIN ... COMMIT section.
save_temporary_tables is now thread safe
Relay_log_info::sleep_lock -> rpl_group_info::sleep_lock
Relay_log_info::sleep_cond -> rpl_group_info::sleep_cond
Relay_log_info->sql_thd renamed to Relay_log_info->sql_driver_thd to avoid wrong usage for merged code
is_in_group() is now independent of state of executed transaction.
sql/slave.cc:
Simplifed arguments to io_salve_killed(), sql_slave_killed() and check_io_slave_killed(); No reason to supply THD as this is part of the given structure.
set_thd_in_use_temporary_tables() removed as in_use is set on usage in sql_base.cc
sql_thd -> sql_driver_thd
More DBUG
Added update_state_of_relay_log() which will calculate the IN_STMT and IN_TRANSACTION state of the relay log after the current element is executed.
If slave_skip_counter is set run things in single threaded mode.
Simplifed arguments to io_salve_killed(), check_io_slave_killed() and sql_slave_killed(); No reason to supply THD as this is part of the given structure.
Added information to thd_proc_info() which thread is waiting for slave mutex to exit.
Disabled not used function rpl_connect_master()
Updated argument to next_event()
sql/sql_base.cc:
Added mutex around usage of slave's temporary tables. The active list is always kept up to date in sql->rgi_slave->save_temporary_tables.
Clear thd->temporary_tables after query (safety)
More DBUG
When using temporary table, set table->in_use to current thd as the THD may be different for slave threads.
Some code is ifdef:ed with REMOVE_AFTER_MERGE_WITH_10 as the given code in 10.0 is not yet in this tree.
In open_table() reuse code from find_temporary_table()
sql/sql_binlog.cc:
rli->sql_thd -> rli->sql_driver_thd
Remove duplicate setting of rgi->rli
sql/sql_class.cc:
Added helper functions rgi_lock_temporary_tables() and rgi_unlock_temporary_tables()
Would have been nicer to have these inline, but there was no easy way to do that
sql/sql_class.h:
Added functions to protect slaves temporary tables
sql/sql_parse.cc:
Added DBUG_PRINT
sql/transaction.cc:
Added comment
2013-10-13 23:24:05 +02:00
|
|
|
DBUG_ENTER("Relay_log_info::stmt_done");
|
2007-04-12 08:58:04 +02:00
|
|
|
|
2016-09-22 08:26:45 +02:00
|
|
|
DBUG_ASSERT(!belongs_to_client());
|
2013-07-03 19:03:21 +02:00
|
|
|
DBUG_ASSERT(rgi->rli == this);
|
2007-04-12 08:58:04 +02:00
|
|
|
/*
|
|
|
|
If in a transaction, and if the slave supports transactions, just
|
|
|
|
inc_event_relay_log_pos(). We only have to check for OPTION_BEGIN
|
|
|
|
(not OPTION_NOT_AUTOCOMMIT) as transactions are logged with
|
|
|
|
BEGIN/COMMIT, not with SET AUTOCOMMIT= .
|
|
|
|
|
Fixes for parallel slave:
- Made slaves temporary table multi-thread slave safe by adding mutex around save_temporary_table usage.
- rli->save_temporary_tables is the active list of all used temporary tables
- This is copied to THD->temporary_tables when temporary tables are opened and updated when temporary tables are closed
- Added THD->lock_temporary_tables() and THD->unlock_temporary_tables() to simplify this.
- Relay_log_info->sql_thd renamed to Relay_log_info->sql_driver_thd to avoid wrong usage for merged code.
- Added is_part_of_group() to mark functions that are part of the next function. This replaces setting IN_STMT when events are executed.
- Added is_begin(), is_commit() and is_rollback() functions to Query_log_event to simplify code.
- If slave_skip_counter is set run things in single threaded mode. This simplifies code for skipping events.
- Updating state of relay log (IN_STMT and IN_TRANSACTION) is moved to one single function: update_state_of_relay_log()
We can't use OPTION_BEGIN to check for the state anymore as the sql_driver and sql execution threads may be different.
Clear IN_STMT and IN_TRANSACTION in init_relay_log_pos() and Relay_log_info::cleanup_context() to ensure the flags doesn't survive slave restarts
is_in_group() is now independent of state of executed transaction.
- Reset thd->transaction.all.modified_non_trans_table() if we did set it for single table row events.
This was mainly for keeping the flag as documented.
- Changed slave_open_temp_tables to uint32 to be able to use atomic operators on it.
- Relay_log_info::sleep_lock -> rpl_group_info::sleep_lock
- Relay_log_info::sleep_cond -> rpl_group_info::sleep_cond
- Changed some functions to take rpl_group_info instead of Relay_log_info to make them multi-slave safe and to simplify usage
- do_shall_skip()
- continue_group()
- sql_slave_killed()
- next_event()
- Simplifed arguments to io_salve_killed(), check_io_slave_killed() and sql_slave_killed(); No reason to supply THD as this is part of the given structure.
- set_thd_in_use_temporary_tables() removed as in_use is set on usage
- Added information to thd_proc_info() which thread is waiting for slave mutex to exit.
- In open_table() reuse code from find_temporary_table()
Other things:
- More DBUG statements
- Fixed the rpl_incident.test can be run with --debug
- More comments
- Disabled not used function rpl_connect_master()
mysql-test/suite/perfschema/r/all_instances.result:
Moved sleep_lock and sleep_cond to rpl_group_info
mysql-test/suite/rpl/r/rpl_incident.result:
Updated result
mysql-test/suite/rpl/t/rpl_incident-master.opt:
Not needed anymore
mysql-test/suite/rpl/t/rpl_incident.test:
Fixed that test can be run with --debug
sql/handler.cc:
More DBUG_PRINT
sql/log.cc:
More comments
sql/log_event.cc:
Added DBUG statements
do_shall_skip(), continue_group() now takes rpl_group_info param
Use is_begin(), is_commit() and is_rollback() functions instead of inspecting query string
We don't have set slaves temporary tables 'in_use' as this is now done when tables are opened.
Removed IN_STMT flag setting. This is now done in update_state_of_relay_log()
Use IN_TRANSACTION flag to test state of relay log.
In rows_event_stmt_cleanup() reset thd->transaction.all.modified_non_trans_table if we had set this before.
sql/log_event.h:
do_shall_skip(), continue_group() now takes rpl_group_info param
Added is_part_of_group() to mark events that are part of the next event. This replaces setting IN_STMT when events are executed.
Added is_begin(), is_commit() and is_rollback() functions to Query_log_event to simplify code.
sql/log_event_old.cc:
Removed IN_STMT flag setting. This is now done in update_state_of_relay_log()
do_shall_skip(), continue_group() now takes rpl_group_info param
sql/log_event_old.h:
Added is_part_of_group() to mark events that are part of the next event.
do_shall_skip(), continue_group() now takes rpl_group_info param
sql/mysqld.cc:
Changed slave_open_temp_tables to uint32 to be able to use atomic operators on it.
Relay_log_info::sleep_lock -> Rpl_group_info::sleep_lock
Relay_log_info::sleep_cond -> Rpl_group_info::sleep_cond
sql/mysqld.h:
Updated types and names
sql/rpl_gtid.cc:
More DBUG
sql/rpl_parallel.cc:
Updated TODO section
Set thd for event that is execution
Use new is_begin(), is_commit() and is_rollback() functions.
More comments
sql/rpl_rli.cc:
sql_thd -> sql_driver_thd
Relay_log_info::sleep_lock -> rpl_group_info::sleep_lock
Relay_log_info::sleep_cond -> rpl_group_info::sleep_cond
Clear IN_STMT and IN_TRANSACTION in init_relay_log_pos() and Relay_log_info::cleanup_context() to ensure the flags doesn't survive slave restarts.
Reset table->in_use for temporary tables as the table may have been used by another THD.
Use IN_TRANSACTION instead of OPTION_BEGIN to check state of relay log.
Removed IN_STMT flag setting. This is now done in update_state_of_relay_log()
sql/rpl_rli.h:
Changed relay log state flags to bit masks instead of bit positions (most other code we have uses bit masks)
Added IN_TRANSACTION to mark if we are in a BEGIN ... COMMIT section.
save_temporary_tables is now thread safe
Relay_log_info::sleep_lock -> rpl_group_info::sleep_lock
Relay_log_info::sleep_cond -> rpl_group_info::sleep_cond
Relay_log_info->sql_thd renamed to Relay_log_info->sql_driver_thd to avoid wrong usage for merged code
is_in_group() is now independent of state of executed transaction.
sql/slave.cc:
Simplifed arguments to io_salve_killed(), sql_slave_killed() and check_io_slave_killed(); No reason to supply THD as this is part of the given structure.
set_thd_in_use_temporary_tables() removed as in_use is set on usage in sql_base.cc
sql_thd -> sql_driver_thd
More DBUG
Added update_state_of_relay_log() which will calculate the IN_STMT and IN_TRANSACTION state of the relay log after the current element is executed.
If slave_skip_counter is set run things in single threaded mode.
Simplifed arguments to io_salve_killed(), check_io_slave_killed() and sql_slave_killed(); No reason to supply THD as this is part of the given structure.
Added information to thd_proc_info() which thread is waiting for slave mutex to exit.
Disabled not used function rpl_connect_master()
Updated argument to next_event()
sql/sql_base.cc:
Added mutex around usage of slave's temporary tables. The active list is always kept up to date in sql->rgi_slave->save_temporary_tables.
Clear thd->temporary_tables after query (safety)
More DBUG
When using temporary table, set table->in_use to current thd as the THD may be different for slave threads.
Some code is ifdef:ed with REMOVE_AFTER_MERGE_WITH_10 as the given code in 10.0 is not yet in this tree.
In open_table() reuse code from find_temporary_table()
sql/sql_binlog.cc:
rli->sql_thd -> rli->sql_driver_thd
Remove duplicate setting of rgi->rli
sql/sql_class.cc:
Added helper functions rgi_lock_temporary_tables() and rgi_unlock_temporary_tables()
Would have been nicer to have these inline, but there was no easy way to do that
sql/sql_class.h:
Added functions to protect slaves temporary tables
sql/sql_parse.cc:
Added DBUG_PRINT
sql/transaction.cc:
Added comment
2013-10-13 23:24:05 +02:00
|
|
|
We can't use rgi->rli->get_flag(IN_TRANSACTION) here as OPTION_BEGIN
|
|
|
|
is also used for single row transactions.
|
|
|
|
|
2007-04-12 08:58:04 +02:00
|
|
|
CAUTION: opt_using_transactions means innodb || bdb ; suppose the
|
|
|
|
master supports InnoDB and BDB, but the slave supports only BDB,
|
|
|
|
problems will arise: - suppose an InnoDB table is created on the
|
|
|
|
master, - then it will be MyISAM on the slave - but as
|
|
|
|
opt_using_transactions is true, the slave will believe he is
|
|
|
|
transactional with the MyISAM table. And problems will come when
|
|
|
|
one does START SLAVE; STOP SLAVE; START SLAVE; (the slave will
|
|
|
|
resume at BEGIN whereas there has not been any rollback). This is
|
|
|
|
the problem of using opt_using_transactions instead of a finer
|
|
|
|
"does the slave support _transactional handler used on the
|
|
|
|
master_".
|
|
|
|
|
|
|
|
More generally, we'll have problems when a query mixes a
|
|
|
|
transactional handler and MyISAM and STOP SLAVE is issued in the
|
|
|
|
middle of the "transaction". START SLAVE will resume at BEGIN
|
|
|
|
while the MyISAM table has already been updated.
|
|
|
|
*/
|
Fixes for parallel slave:
- Made slaves temporary table multi-thread slave safe by adding mutex around save_temporary_table usage.
- rli->save_temporary_tables is the active list of all used temporary tables
- This is copied to THD->temporary_tables when temporary tables are opened and updated when temporary tables are closed
- Added THD->lock_temporary_tables() and THD->unlock_temporary_tables() to simplify this.
- Relay_log_info->sql_thd renamed to Relay_log_info->sql_driver_thd to avoid wrong usage for merged code.
- Added is_part_of_group() to mark functions that are part of the next function. This replaces setting IN_STMT when events are executed.
- Added is_begin(), is_commit() and is_rollback() functions to Query_log_event to simplify code.
- If slave_skip_counter is set run things in single threaded mode. This simplifies code for skipping events.
- Updating state of relay log (IN_STMT and IN_TRANSACTION) is moved to one single function: update_state_of_relay_log()
We can't use OPTION_BEGIN to check for the state anymore as the sql_driver and sql execution threads may be different.
Clear IN_STMT and IN_TRANSACTION in init_relay_log_pos() and Relay_log_info::cleanup_context() to ensure the flags doesn't survive slave restarts
is_in_group() is now independent of state of executed transaction.
- Reset thd->transaction.all.modified_non_trans_table() if we did set it for single table row events.
This was mainly for keeping the flag as documented.
- Changed slave_open_temp_tables to uint32 to be able to use atomic operators on it.
- Relay_log_info::sleep_lock -> rpl_group_info::sleep_lock
- Relay_log_info::sleep_cond -> rpl_group_info::sleep_cond
- Changed some functions to take rpl_group_info instead of Relay_log_info to make them multi-slave safe and to simplify usage
- do_shall_skip()
- continue_group()
- sql_slave_killed()
- next_event()
- Simplifed arguments to io_salve_killed(), check_io_slave_killed() and sql_slave_killed(); No reason to supply THD as this is part of the given structure.
- set_thd_in_use_temporary_tables() removed as in_use is set on usage
- Added information to thd_proc_info() which thread is waiting for slave mutex to exit.
- In open_table() reuse code from find_temporary_table()
Other things:
- More DBUG statements
- Fixed the rpl_incident.test can be run with --debug
- More comments
- Disabled not used function rpl_connect_master()
mysql-test/suite/perfschema/r/all_instances.result:
Moved sleep_lock and sleep_cond to rpl_group_info
mysql-test/suite/rpl/r/rpl_incident.result:
Updated result
mysql-test/suite/rpl/t/rpl_incident-master.opt:
Not needed anymore
mysql-test/suite/rpl/t/rpl_incident.test:
Fixed that test can be run with --debug
sql/handler.cc:
More DBUG_PRINT
sql/log.cc:
More comments
sql/log_event.cc:
Added DBUG statements
do_shall_skip(), continue_group() now takes rpl_group_info param
Use is_begin(), is_commit() and is_rollback() functions instead of inspecting query string
We don't have set slaves temporary tables 'in_use' as this is now done when tables are opened.
Removed IN_STMT flag setting. This is now done in update_state_of_relay_log()
Use IN_TRANSACTION flag to test state of relay log.
In rows_event_stmt_cleanup() reset thd->transaction.all.modified_non_trans_table if we had set this before.
sql/log_event.h:
do_shall_skip(), continue_group() now takes rpl_group_info param
Added is_part_of_group() to mark events that are part of the next event. This replaces setting IN_STMT when events are executed.
Added is_begin(), is_commit() and is_rollback() functions to Query_log_event to simplify code.
sql/log_event_old.cc:
Removed IN_STMT flag setting. This is now done in update_state_of_relay_log()
do_shall_skip(), continue_group() now takes rpl_group_info param
sql/log_event_old.h:
Added is_part_of_group() to mark events that are part of the next event.
do_shall_skip(), continue_group() now takes rpl_group_info param
sql/mysqld.cc:
Changed slave_open_temp_tables to uint32 to be able to use atomic operators on it.
Relay_log_info::sleep_lock -> Rpl_group_info::sleep_lock
Relay_log_info::sleep_cond -> Rpl_group_info::sleep_cond
sql/mysqld.h:
Updated types and names
sql/rpl_gtid.cc:
More DBUG
sql/rpl_parallel.cc:
Updated TODO section
Set thd for event that is execution
Use new is_begin(), is_commit() and is_rollback() functions.
More comments
sql/rpl_rli.cc:
sql_thd -> sql_driver_thd
Relay_log_info::sleep_lock -> rpl_group_info::sleep_lock
Relay_log_info::sleep_cond -> rpl_group_info::sleep_cond
Clear IN_STMT and IN_TRANSACTION in init_relay_log_pos() and Relay_log_info::cleanup_context() to ensure the flags doesn't survive slave restarts.
Reset table->in_use for temporary tables as the table may have been used by another THD.
Use IN_TRANSACTION instead of OPTION_BEGIN to check state of relay log.
Removed IN_STMT flag setting. This is now done in update_state_of_relay_log()
sql/rpl_rli.h:
Changed relay log state flags to bit masks instead of bit positions (most other code we have uses bit masks)
Added IN_TRANSACTION to mark if we are in a BEGIN ... COMMIT section.
save_temporary_tables is now thread safe
Relay_log_info::sleep_lock -> rpl_group_info::sleep_lock
Relay_log_info::sleep_cond -> rpl_group_info::sleep_cond
Relay_log_info->sql_thd renamed to Relay_log_info->sql_driver_thd to avoid wrong usage for merged code
is_in_group() is now independent of state of executed transaction.
sql/slave.cc:
Simplifed arguments to io_salve_killed(), sql_slave_killed() and check_io_slave_killed(); No reason to supply THD as this is part of the given structure.
set_thd_in_use_temporary_tables() removed as in_use is set on usage in sql_base.cc
sql_thd -> sql_driver_thd
More DBUG
Added update_state_of_relay_log() which will calculate the IN_STMT and IN_TRANSACTION state of the relay log after the current element is executed.
If slave_skip_counter is set run things in single threaded mode.
Simplifed arguments to io_salve_killed(), check_io_slave_killed() and sql_slave_killed(); No reason to supply THD as this is part of the given structure.
Added information to thd_proc_info() which thread is waiting for slave mutex to exit.
Disabled not used function rpl_connect_master()
Updated argument to next_event()
sql/sql_base.cc:
Added mutex around usage of slave's temporary tables. The active list is always kept up to date in sql->rgi_slave->save_temporary_tables.
Clear thd->temporary_tables after query (safety)
More DBUG
When using temporary table, set table->in_use to current thd as the THD may be different for slave threads.
Some code is ifdef:ed with REMOVE_AFTER_MERGE_WITH_10 as the given code in 10.0 is not yet in this tree.
In open_table() reuse code from find_temporary_table()
sql/sql_binlog.cc:
rli->sql_thd -> rli->sql_driver_thd
Remove duplicate setting of rgi->rli
sql/sql_class.cc:
Added helper functions rgi_lock_temporary_tables() and rgi_unlock_temporary_tables()
Would have been nicer to have these inline, but there was no easy way to do that
sql/sql_class.h:
Added functions to protect slaves temporary tables
sql/sql_parse.cc:
Added DBUG_PRINT
sql/transaction.cc:
Added comment
2013-10-13 23:24:05 +02:00
|
|
|
if ((rgi->thd->variables.option_bits & OPTION_BEGIN) &&
|
|
|
|
opt_using_transactions)
|
2013-10-17 14:11:19 +02:00
|
|
|
rgi->inc_event_relay_log_pos();
|
2007-04-12 08:58:04 +02:00
|
|
|
else
|
|
|
|
{
|
2013-10-17 14:11:19 +02:00
|
|
|
inc_group_relay_log_pos(event_master_log_pos, rgi);
|
2015-11-29 16:51:23 +01:00
|
|
|
if (rpl_global_gtid_slave_state->record_and_update_gtid(thd, rgi))
|
2013-03-21 17:33:29 +01:00
|
|
|
{
|
2014-06-25 15:17:03 +02:00
|
|
|
report(WARNING_LEVEL, ER_CANNOT_UPDATE_GTID_STATE, rgi->gtid_info(),
|
2013-03-21 17:33:29 +01:00
|
|
|
"Failed to update GTID state in %s.%s, slave state may become "
|
|
|
|
"inconsistent: %d: %s",
|
|
|
|
"mysql", rpl_gtid_slave_state_table_name.str,
|
2013-07-21 16:39:19 +02:00
|
|
|
thd->get_stmt_da()->sql_errno(), thd->get_stmt_da()->message());
|
2013-03-21 17:33:29 +01:00
|
|
|
/*
|
|
|
|
At this point we are not in a transaction (for example after DDL),
|
|
|
|
so we can not roll back. Anyway, normally updates to the slave
|
|
|
|
state table should not fail, and if they do, at least we made the
|
|
|
|
DBA aware of the problem in the error log.
|
|
|
|
*/
|
|
|
|
}
|
2013-03-28 13:03:51 +01:00
|
|
|
DBUG_EXECUTE_IF("inject_crash_before_flush_rli", DBUG_SUICIDE(););
|
2013-10-25 12:56:12 +02:00
|
|
|
if (mi->using_gtid == Master_info::USE_GTID_NO)
|
2017-03-30 12:48:42 +02:00
|
|
|
if (flush())
|
2017-02-05 01:23:49 +01:00
|
|
|
error= 1;
|
2013-03-28 13:03:51 +01:00
|
|
|
DBUG_EXECUTE_IF("inject_crash_after_flush_rli", DBUG_SUICIDE(););
|
2007-04-12 08:58:04 +02:00
|
|
|
}
|
2017-02-05 01:23:49 +01:00
|
|
|
DBUG_RETURN(error);
|
2007-02-26 17:44:55 +01:00
|
|
|
}
|
|
|
|
|
2014-05-08 14:20:18 +02:00
|
|
|
|
|
|
|
int
|
|
|
|
Relay_log_info::alloc_inuse_relaylog(const char *name)
|
|
|
|
{
|
|
|
|
inuse_relaylog *ir;
|
MDEV-6589: Incorrect relay log start position when restarting SQL thread after error in parallel replication
The problem occurs in parallel replication in GTID mode, when we are using
multiple replication domains. In this case, if the SQL thread stops, the
slave GTID position may refer to a different point in the relay log for each
domain.
The bug was that when the SQL thread was stopped and restarted (but the IO
thread was kept running), the SQL thread would resume applying the relay log
from the point of the most advanced replication domain, silently skipping all
earlier events within other domains. This caused replication corruption.
This patch solves the problem by storing, when the SQL thread stops with
multiple parallel replication domains active, the current GTID
position. Additionally, the current position in the relay logs is moved back
to a point known to be earlier than the current position of any replication
domain. Then when the SQL thread restarts from the earlier position, GTIDs
encountered are compared against the stored GTID position. Any GTID that was
already applied before the stop is skipped to avoid duplicate apply.
This patch should have no effect if multi-domain GTID parallel replication is
not used. Similarly, if both SQL and IO thread are stopped and restarted, the
patch has no effect, as in this case the existing relay logs are removed and
re-fetched from the master at the current global @@gtid_slave_pos.
2015-02-18 12:22:50 +01:00
|
|
|
uint32 gtid_count;
|
|
|
|
rpl_gtid *gtid_list;
|
2014-05-08 14:20:18 +02:00
|
|
|
|
|
|
|
if (!(ir= (inuse_relaylog *)my_malloc(sizeof(*ir), MYF(MY_WME|MY_ZEROFILL))))
|
|
|
|
{
|
|
|
|
my_error(ER_OUTOFMEMORY, MYF(0), (int)sizeof(*ir));
|
|
|
|
return 1;
|
|
|
|
}
|
MDEV-6589: Incorrect relay log start position when restarting SQL thread after error in parallel replication
The problem occurs in parallel replication in GTID mode, when we are using
multiple replication domains. In this case, if the SQL thread stops, the
slave GTID position may refer to a different point in the relay log for each
domain.
The bug was that when the SQL thread was stopped and restarted (but the IO
thread was kept running), the SQL thread would resume applying the relay log
from the point of the most advanced replication domain, silently skipping all
earlier events within other domains. This caused replication corruption.
This patch solves the problem by storing, when the SQL thread stops with
multiple parallel replication domains active, the current GTID
position. Additionally, the current position in the relay logs is moved back
to a point known to be earlier than the current position of any replication
domain. Then when the SQL thread restarts from the earlier position, GTIDs
encountered are compared against the stored GTID position. Any GTID that was
already applied before the stop is skipped to avoid duplicate apply.
This patch should have no effect if multi-domain GTID parallel replication is
not used. Similarly, if both SQL and IO thread are stopped and restarted, the
patch has no effect, as in this case the existing relay logs are removed and
re-fetched from the master at the current global @@gtid_slave_pos.
2015-02-18 12:22:50 +01:00
|
|
|
gtid_count= relay_log_state.count();
|
|
|
|
if (!(gtid_list= (rpl_gtid *)my_malloc(sizeof(*gtid_list)*gtid_count,
|
|
|
|
MYF(MY_WME))))
|
|
|
|
{
|
|
|
|
my_free(ir);
|
|
|
|
my_error(ER_OUTOFMEMORY, MYF(0), (int)sizeof(*gtid_list)*gtid_count);
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
if (relay_log_state.get_gtid_list(gtid_list, gtid_count))
|
|
|
|
{
|
|
|
|
my_free(gtid_list);
|
|
|
|
my_free(ir);
|
|
|
|
DBUG_ASSERT(0 /* Should not be possible as we allocated correct length */);
|
|
|
|
my_error(ER_OUT_OF_RESOURCES, MYF(0));
|
|
|
|
return 1;
|
|
|
|
}
|
2014-11-13 10:20:48 +01:00
|
|
|
ir->rli= this;
|
2014-07-08 12:54:47 +02:00
|
|
|
strmake_buf(ir->name, name);
|
MDEV-6589: Incorrect relay log start position when restarting SQL thread after error in parallel replication
The problem occurs in parallel replication in GTID mode, when we are using
multiple replication domains. In this case, if the SQL thread stops, the
slave GTID position may refer to a different point in the relay log for each
domain.
The bug was that when the SQL thread was stopped and restarted (but the IO
thread was kept running), the SQL thread would resume applying the relay log
from the point of the most advanced replication domain, silently skipping all
earlier events within other domains. This caused replication corruption.
This patch solves the problem by storing, when the SQL thread stops with
multiple parallel replication domains active, the current GTID
position. Additionally, the current position in the relay logs is moved back
to a point known to be earlier than the current position of any replication
domain. Then when the SQL thread restarts from the earlier position, GTIDs
encountered are compared against the stored GTID position. Any GTID that was
already applied before the stop is skipped to avoid duplicate apply.
This patch should have no effect if multi-domain GTID parallel replication is
not used. Similarly, if both SQL and IO thread are stopped and restarted, the
patch has no effect, as in this case the existing relay logs are removed and
re-fetched from the master at the current global @@gtid_slave_pos.
2015-02-18 12:22:50 +01:00
|
|
|
ir->relay_log_state= gtid_list;
|
|
|
|
ir->relay_log_state_count= gtid_count;
|
2014-05-08 14:20:18 +02:00
|
|
|
|
|
|
|
if (!inuse_relaylog_list)
|
|
|
|
inuse_relaylog_list= ir;
|
|
|
|
else
|
2014-05-15 15:52:08 +02:00
|
|
|
{
|
|
|
|
last_inuse_relaylog->completed= true;
|
2014-05-08 14:20:18 +02:00
|
|
|
last_inuse_relaylog->next= ir;
|
2014-05-15 15:52:08 +02:00
|
|
|
}
|
2014-05-08 14:20:18 +02:00
|
|
|
last_inuse_relaylog= ir;
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
|
MDEV-6589: Incorrect relay log start position when restarting SQL thread after error in parallel replication
The problem occurs in parallel replication in GTID mode, when we are using
multiple replication domains. In this case, if the SQL thread stops, the
slave GTID position may refer to a different point in the relay log for each
domain.
The bug was that when the SQL thread was stopped and restarted (but the IO
thread was kept running), the SQL thread would resume applying the relay log
from the point of the most advanced replication domain, silently skipping all
earlier events within other domains. This caused replication corruption.
This patch solves the problem by storing, when the SQL thread stops with
multiple parallel replication domains active, the current GTID
position. Additionally, the current position in the relay logs is moved back
to a point known to be earlier than the current position of any replication
domain. Then when the SQL thread restarts from the earlier position, GTIDs
encountered are compared against the stored GTID position. Any GTID that was
already applied before the stop is skipped to avoid duplicate apply.
This patch should have no effect if multi-domain GTID parallel replication is
not used. Similarly, if both SQL and IO thread are stopped and restarted, the
patch has no effect, as in this case the existing relay logs are removed and
re-fetched from the master at the current global @@gtid_slave_pos.
2015-02-18 12:22:50 +01:00
|
|
|
void
|
|
|
|
Relay_log_info::free_inuse_relaylog(inuse_relaylog *ir)
|
|
|
|
{
|
|
|
|
my_free(ir->relay_log_state);
|
|
|
|
my_free(ir);
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
void
|
|
|
|
Relay_log_info::reset_inuse_relaylog()
|
|
|
|
{
|
|
|
|
inuse_relaylog *cur= inuse_relaylog_list;
|
|
|
|
while (cur)
|
|
|
|
{
|
|
|
|
DBUG_ASSERT(cur->queued_count == cur->dequeued_count);
|
|
|
|
inuse_relaylog *next= cur->next;
|
|
|
|
free_inuse_relaylog(cur);
|
|
|
|
cur= next;
|
|
|
|
}
|
|
|
|
inuse_relaylog_list= last_inuse_relaylog= NULL;
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
int
|
|
|
|
Relay_log_info::update_relay_log_state(rpl_gtid *gtid_list, uint32 count)
|
|
|
|
{
|
|
|
|
int res= 0;
|
|
|
|
while (count)
|
|
|
|
{
|
|
|
|
if (relay_log_state.update_nolock(gtid_list, false))
|
|
|
|
res= 1;
|
|
|
|
++gtid_list;
|
|
|
|
--count;
|
|
|
|
}
|
|
|
|
return res;
|
|
|
|
}
|
|
|
|
|
|
|
|
|
2006-10-31 12:23:14 +01:00
|
|
|
#if !defined(MYSQL_CLIENT) && defined(HAVE_REPLICATION)
|
2017-03-09 13:27:27 +01:00
|
|
|
struct gtid_pos_element { uint64 sub_id; rpl_gtid gtid; void *hton; };
|
2017-03-06 15:32:54 +01:00
|
|
|
|
|
|
|
static int
|
|
|
|
scan_one_gtid_slave_pos_table(THD *thd, HASH *hash, DYNAMIC_ARRAY *array,
|
2017-07-03 10:36:09 +02:00
|
|
|
LEX_CSTRING *tablename, void **out_hton)
|
2013-03-18 15:09:36 +01:00
|
|
|
{
|
|
|
|
TABLE_LIST tlist;
|
2018-04-11 01:20:22 +02:00
|
|
|
TABLE *UNINIT_VAR(table);
|
2013-03-18 15:09:36 +01:00
|
|
|
bool table_opened= false;
|
|
|
|
bool table_scanned= false;
|
2017-03-06 15:32:54 +01:00
|
|
|
struct gtid_pos_element tmp_entry, *entry;
|
2013-03-18 15:09:36 +01:00
|
|
|
int err= 0;
|
|
|
|
|
2015-04-15 16:32:34 +02:00
|
|
|
thd->reset_for_next_command();
|
2018-01-07 17:03:44 +01:00
|
|
|
tlist.init_one_table(&MYSQL_SCHEMA_NAME, tablename, NULL, TL_READ);
|
2013-03-18 15:09:36 +01:00
|
|
|
if ((err= open_and_lock_tables(thd, &tlist, FALSE, 0)))
|
|
|
|
goto end;
|
|
|
|
table_opened= true;
|
|
|
|
table= tlist.table;
|
|
|
|
|
|
|
|
if ((err= gtid_check_rpl_slave_state_table(table)))
|
|
|
|
goto end;
|
|
|
|
|
|
|
|
bitmap_set_all(table->read_set);
|
2018-04-11 02:18:03 +02:00
|
|
|
if (unlikely(err= table->file->ha_rnd_init_with_error(1)))
|
2013-03-18 15:09:36 +01:00
|
|
|
goto end;
|
2018-04-11 02:18:03 +02:00
|
|
|
|
2013-03-18 15:09:36 +01:00
|
|
|
table_scanned= true;
|
|
|
|
for (;;)
|
|
|
|
{
|
|
|
|
uint32 domain_id, server_id;
|
|
|
|
uint64 sub_id, seq_no;
|
|
|
|
uchar *rec;
|
|
|
|
|
|
|
|
if ((err= table->file->ha_rnd_next(table->record[0])))
|
|
|
|
{
|
2018-04-14 00:09:11 +02:00
|
|
|
if (err == HA_ERR_END_OF_FILE)
|
2013-03-18 15:09:36 +01:00
|
|
|
break;
|
|
|
|
else
|
2013-06-03 07:41:38 +02:00
|
|
|
{
|
|
|
|
table->file->print_error(err, MYF(0));
|
2013-03-18 15:09:36 +01:00
|
|
|
goto end;
|
2013-06-03 07:41:38 +02:00
|
|
|
}
|
2013-03-18 15:09:36 +01:00
|
|
|
}
|
2017-09-28 12:38:02 +02:00
|
|
|
domain_id= (uint32)table->field[0]->val_int();
|
2013-03-18 15:09:36 +01:00
|
|
|
sub_id= (ulonglong)table->field[1]->val_int();
|
2017-09-28 12:38:02 +02:00
|
|
|
server_id= (uint32)table->field[2]->val_int();
|
2013-03-18 15:09:36 +01:00
|
|
|
seq_no= (ulonglong)table->field[3]->val_int();
|
2019-10-21 17:41:58 +02:00
|
|
|
DBUG_PRINT("info", ("Read slave state row: %u-%u-%lu sub_id=%lu",
|
2013-03-18 15:09:36 +01:00
|
|
|
(unsigned)domain_id, (unsigned)server_id,
|
|
|
|
(ulong)seq_no, (ulong)sub_id));
|
|
|
|
|
2013-06-21 21:23:24 +02:00
|
|
|
tmp_entry.sub_id= sub_id;
|
|
|
|
tmp_entry.gtid.domain_id= domain_id;
|
|
|
|
tmp_entry.gtid.server_id= server_id;
|
|
|
|
tmp_entry.gtid.seq_no= seq_no;
|
2017-03-09 13:27:27 +01:00
|
|
|
tmp_entry.hton= table->s->db_type();
|
2017-03-06 15:32:54 +01:00
|
|
|
if ((err= insert_dynamic(array, (uchar *)&tmp_entry)))
|
2013-06-21 21:23:24 +02:00
|
|
|
{
|
|
|
|
my_error(ER_OUT_OF_RESOURCES, MYF(0));
|
|
|
|
goto end;
|
|
|
|
}
|
|
|
|
|
2017-03-06 15:32:54 +01:00
|
|
|
if ((rec= my_hash_search(hash, (const uchar *)&domain_id, 0)))
|
2013-03-18 15:09:36 +01:00
|
|
|
{
|
2017-03-06 15:32:54 +01:00
|
|
|
entry= (struct gtid_pos_element *)rec;
|
2013-03-18 15:09:36 +01:00
|
|
|
if (entry->sub_id >= sub_id)
|
|
|
|
continue;
|
2013-03-28 13:03:51 +01:00
|
|
|
entry->sub_id= sub_id;
|
|
|
|
DBUG_ASSERT(entry->gtid.domain_id == domain_id);
|
|
|
|
entry->gtid.server_id= server_id;
|
|
|
|
entry->gtid.seq_no= seq_no;
|
2017-03-09 13:27:27 +01:00
|
|
|
entry->hton= table->s->db_type();
|
2013-03-18 15:09:36 +01:00
|
|
|
}
|
|
|
|
else
|
|
|
|
{
|
2017-03-06 15:32:54 +01:00
|
|
|
if (!(entry= (struct gtid_pos_element *)my_malloc(sizeof(*entry),
|
|
|
|
MYF(MY_WME))))
|
2013-03-18 15:09:36 +01:00
|
|
|
{
|
2013-06-03 07:41:38 +02:00
|
|
|
my_error(ER_OUTOFMEMORY, MYF(0), (int)sizeof(*entry));
|
2013-03-18 15:09:36 +01:00
|
|
|
err= 1;
|
|
|
|
goto end;
|
|
|
|
}
|
2013-03-28 13:03:51 +01:00
|
|
|
entry->sub_id= sub_id;
|
|
|
|
entry->gtid.domain_id= domain_id;
|
|
|
|
entry->gtid.server_id= server_id;
|
|
|
|
entry->gtid.seq_no= seq_no;
|
2017-03-09 13:27:27 +01:00
|
|
|
entry->hton= table->s->db_type();
|
2017-03-06 15:32:54 +01:00
|
|
|
if ((err= my_hash_insert(hash, (uchar *)entry)))
|
2013-03-18 15:09:36 +01:00
|
|
|
{
|
|
|
|
my_free(entry);
|
2013-06-03 07:41:38 +02:00
|
|
|
my_error(ER_OUT_OF_RESOURCES, MYF(0));
|
2013-03-18 15:09:36 +01:00
|
|
|
goto end;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
2017-03-06 15:32:54 +01:00
|
|
|
err= 0; /* Clear HA_ERR_END_OF_FILE */
|
|
|
|
|
|
|
|
end:
|
|
|
|
if (table_scanned)
|
|
|
|
{
|
|
|
|
table->file->ha_index_or_rnd_end();
|
|
|
|
ha_commit_trans(thd, FALSE);
|
|
|
|
ha_commit_trans(thd, TRUE);
|
|
|
|
}
|
|
|
|
if (table_opened)
|
|
|
|
{
|
2017-03-09 12:16:15 +01:00
|
|
|
*out_hton= table->s->db_type();
|
2017-03-06 15:32:54 +01:00
|
|
|
close_thread_tables(thd);
|
|
|
|
thd->mdl_context.release_transactional_locks();
|
|
|
|
}
|
|
|
|
return err;
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
Look for all tables mysql.gtid_slave_pos*. Read all rows from each such
|
|
|
|
table found into ARRAY. For each domain id, put the row with highest sub_id
|
|
|
|
into HASH.
|
|
|
|
*/
|
|
|
|
static int
|
2017-07-03 10:36:09 +02:00
|
|
|
scan_all_gtid_slave_pos_table(THD *thd, int (*cb)(THD *, LEX_CSTRING *, void *),
|
2017-03-08 13:56:29 +01:00
|
|
|
void *cb_data)
|
2017-03-06 15:32:54 +01:00
|
|
|
{
|
|
|
|
char path[FN_REFLEN];
|
|
|
|
MY_DIR *dirp;
|
|
|
|
|
|
|
|
thd->reset_for_next_command();
|
2018-01-07 17:03:44 +01:00
|
|
|
if (lock_schema_name(thd, MYSQL_SCHEMA_NAME.str))
|
2017-03-06 15:32:54 +01:00
|
|
|
return 1;
|
|
|
|
|
2018-01-07 17:03:44 +01:00
|
|
|
build_table_filename(path, sizeof(path) - 1, MYSQL_SCHEMA_NAME.str, "", "", 0);
|
2017-03-06 15:32:54 +01:00
|
|
|
if (!(dirp= my_dir(path, MYF(MY_DONT_SORT))))
|
|
|
|
{
|
|
|
|
my_error(ER_FILE_NOT_FOUND, MYF(0), path, my_errno);
|
|
|
|
close_thread_tables(thd);
|
|
|
|
thd->mdl_context.release_transactional_locks();
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
else
|
|
|
|
{
|
|
|
|
size_t i;
|
2017-07-03 10:36:09 +02:00
|
|
|
Dynamic_array<LEX_CSTRING*> files(dirp->number_of_files);
|
2017-03-06 15:32:54 +01:00
|
|
|
Discovered_table_list tl(thd, &files);
|
|
|
|
int err;
|
|
|
|
|
2018-01-07 17:03:44 +01:00
|
|
|
err= ha_discover_table_names(thd, &MYSQL_SCHEMA_NAME, dirp, &tl, false);
|
2017-03-06 15:32:54 +01:00
|
|
|
my_dirend(dirp);
|
|
|
|
close_thread_tables(thd);
|
|
|
|
thd->mdl_context.release_transactional_locks();
|
|
|
|
if (err)
|
|
|
|
return err;
|
|
|
|
|
|
|
|
for (i = 0; i < files.elements(); ++i)
|
|
|
|
{
|
|
|
|
if (strncmp(files.at(i)->str,
|
|
|
|
rpl_gtid_slave_state_table_name.str,
|
|
|
|
rpl_gtid_slave_state_table_name.length) == 0)
|
|
|
|
{
|
2017-03-08 13:56:29 +01:00
|
|
|
if ((err= (*cb)(thd, files.at(i), cb_data)))
|
2017-03-06 15:32:54 +01:00
|
|
|
return err;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
|
2017-03-08 13:56:29 +01:00
|
|
|
struct load_gtid_state_cb_data {
|
|
|
|
HASH *hash;
|
|
|
|
DYNAMIC_ARRAY *array;
|
2017-03-09 12:16:15 +01:00
|
|
|
struct rpl_slave_state::gtid_pos_table *table_list;
|
2017-03-14 12:54:10 +01:00
|
|
|
struct rpl_slave_state::gtid_pos_table *default_entry;
|
2017-03-08 13:56:29 +01:00
|
|
|
};
|
|
|
|
|
2017-03-14 12:54:10 +01:00
|
|
|
static int
|
2017-07-03 10:36:09 +02:00
|
|
|
process_gtid_pos_table(THD *thd, LEX_CSTRING *table_name, void *hton,
|
2017-03-14 12:54:10 +01:00
|
|
|
struct load_gtid_state_cb_data *data)
|
|
|
|
{
|
|
|
|
struct rpl_slave_state::gtid_pos_table *p, *entry, **next_ptr;
|
|
|
|
bool is_default=
|
|
|
|
(strcmp(table_name->str, rpl_gtid_slave_state_table_name.str) == 0);
|
|
|
|
|
|
|
|
/*
|
|
|
|
Ignore tables with duplicate storage engine, with a warning.
|
|
|
|
Prefer the default mysql.gtid_slave_pos over another table
|
|
|
|
mysql.gtid_slave_posXXX with the same storage engine.
|
|
|
|
*/
|
|
|
|
next_ptr= &data->table_list;
|
|
|
|
entry= data->table_list;
|
|
|
|
while (entry)
|
|
|
|
{
|
|
|
|
if (entry->table_hton == hton)
|
|
|
|
{
|
|
|
|
static const char *warning_msg= "Ignoring redundant table mysql.%s "
|
|
|
|
"since mysql.%s has the same storage engine";
|
|
|
|
if (!is_default)
|
|
|
|
{
|
|
|
|
/* Ignore the redundant table. */
|
2018-01-29 20:08:44 +01:00
|
|
|
sql_print_warning(warning_msg, table_name->str, entry->table_name.str);
|
2017-03-14 12:54:10 +01:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
else
|
|
|
|
{
|
2018-01-29 20:08:44 +01:00
|
|
|
sql_print_warning(warning_msg, entry->table_name.str, table_name->str);
|
2017-03-14 12:54:10 +01:00
|
|
|
/* Delete the redundant table, and proceed to add this one instead. */
|
|
|
|
*next_ptr= entry->next;
|
|
|
|
my_free(entry);
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
next_ptr= &entry->next;
|
|
|
|
entry= entry->next;
|
|
|
|
}
|
|
|
|
|
2017-03-24 12:07:07 +01:00
|
|
|
p= rpl_global_gtid_slave_state->alloc_gtid_pos_table(table_name,
|
|
|
|
hton, rpl_slave_state::GTID_POS_AVAILABLE);
|
|
|
|
if (!p)
|
2017-03-14 12:54:10 +01:00
|
|
|
return 1;
|
|
|
|
p->next= data->table_list;
|
|
|
|
data->table_list= p;
|
|
|
|
if (is_default)
|
|
|
|
data->default_entry= p;
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
|
2017-03-24 12:07:07 +01:00
|
|
|
/*
|
|
|
|
Put tables corresponding to @@gtid_pos_auto_engines at the end of the list,
|
|
|
|
marked to be auto-created if needed.
|
|
|
|
*/
|
|
|
|
static int
|
|
|
|
gtid_pos_auto_create_tables(rpl_slave_state::gtid_pos_table **list_ptr)
|
|
|
|
{
|
|
|
|
plugin_ref *auto_engines;
|
|
|
|
int err= 0;
|
|
|
|
mysql_mutex_lock(&LOCK_global_system_variables);
|
|
|
|
for (auto_engines= opt_gtid_pos_auto_plugins;
|
|
|
|
!err && auto_engines && *auto_engines;
|
|
|
|
++auto_engines)
|
|
|
|
{
|
|
|
|
void *hton= plugin_hton(*auto_engines);
|
|
|
|
char buf[FN_REFLEN+1];
|
2017-07-03 10:36:09 +02:00
|
|
|
LEX_CSTRING table_name;
|
2017-03-24 12:07:07 +01:00
|
|
|
char *p;
|
|
|
|
rpl_slave_state::gtid_pos_table *entry, **next_ptr;
|
|
|
|
|
|
|
|
/* See if this engine is already in the list. */
|
|
|
|
next_ptr= list_ptr;
|
|
|
|
entry= *list_ptr;
|
|
|
|
while (entry)
|
|
|
|
{
|
|
|
|
if (entry->table_hton == hton)
|
|
|
|
break;
|
|
|
|
next_ptr= &entry->next;
|
|
|
|
entry= entry->next;
|
|
|
|
}
|
|
|
|
if (entry)
|
|
|
|
continue;
|
|
|
|
|
|
|
|
/* Add an auto-create entry for this engine at end of list. */
|
|
|
|
p= strmake(buf, rpl_gtid_slave_state_table_name.str, FN_REFLEN);
|
|
|
|
p= strmake(p, "_", FN_REFLEN - (p - buf));
|
|
|
|
p= strmake(p, plugin_name(*auto_engines)->str, FN_REFLEN - (p - buf));
|
|
|
|
table_name.str= buf;
|
|
|
|
table_name.length= p - buf;
|
2018-05-18 19:32:57 +02:00
|
|
|
table_case_convert(const_cast<char*>(table_name.str),
|
|
|
|
static_cast<uint>(table_name.length));
|
2017-03-24 12:07:07 +01:00
|
|
|
entry= rpl_global_gtid_slave_state->alloc_gtid_pos_table
|
|
|
|
(&table_name, hton, rpl_slave_state::GTID_POS_AUTO_CREATE);
|
|
|
|
if (!entry)
|
|
|
|
{
|
|
|
|
err= 1;
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
*next_ptr= entry;
|
|
|
|
}
|
|
|
|
mysql_mutex_unlock(&LOCK_global_system_variables);
|
|
|
|
return err;
|
|
|
|
}
|
|
|
|
|
|
|
|
|
2017-03-08 13:56:29 +01:00
|
|
|
static int
|
2017-07-03 10:36:09 +02:00
|
|
|
load_gtid_state_cb(THD *thd, LEX_CSTRING *table_name, void *arg)
|
2017-03-08 13:56:29 +01:00
|
|
|
{
|
2017-03-09 12:16:15 +01:00
|
|
|
int err;
|
2017-03-08 13:56:29 +01:00
|
|
|
load_gtid_state_cb_data *data= static_cast<load_gtid_state_cb_data *>(arg);
|
2017-03-09 13:27:27 +01:00
|
|
|
void *hton;
|
2017-03-09 12:16:15 +01:00
|
|
|
|
|
|
|
if ((err= scan_one_gtid_slave_pos_table(thd, data->hash, data->array,
|
|
|
|
table_name, &hton)))
|
|
|
|
return err;
|
2017-03-14 12:54:10 +01:00
|
|
|
return process_gtid_pos_table(thd, table_name, hton, data);
|
2017-03-08 13:56:29 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
|
2017-03-06 15:32:54 +01:00
|
|
|
int
|
|
|
|
rpl_load_gtid_slave_state(THD *thd)
|
|
|
|
{
|
|
|
|
bool array_inited= false;
|
|
|
|
struct gtid_pos_element tmp_entry, *entry;
|
|
|
|
HASH hash;
|
|
|
|
DYNAMIC_ARRAY array;
|
|
|
|
int err= 0;
|
|
|
|
uint32 i;
|
2017-03-08 13:56:29 +01:00
|
|
|
load_gtid_state_cb_data cb_data;
|
2018-10-14 20:41:49 +02:00
|
|
|
rpl_slave_state::list_element *old_gtids_list;
|
2017-03-06 15:32:54 +01:00
|
|
|
DBUG_ENTER("rpl_load_gtid_slave_state");
|
|
|
|
|
|
|
|
mysql_mutex_lock(&rpl_global_gtid_slave_state->LOCK_slave_state);
|
|
|
|
bool loaded= rpl_global_gtid_slave_state->loaded;
|
|
|
|
mysql_mutex_unlock(&rpl_global_gtid_slave_state->LOCK_slave_state);
|
|
|
|
if (loaded)
|
|
|
|
DBUG_RETURN(0);
|
|
|
|
|
2017-03-09 12:16:15 +01:00
|
|
|
cb_data.table_list= NULL;
|
2017-03-14 12:54:10 +01:00
|
|
|
cb_data.default_entry= NULL;
|
2017-03-06 15:32:54 +01:00
|
|
|
my_hash_init(&hash, &my_charset_bin, 32,
|
|
|
|
offsetof(gtid_pos_element, gtid) + offsetof(rpl_gtid, domain_id),
|
|
|
|
sizeof(uint32), NULL, my_free, HASH_UNIQUE);
|
|
|
|
if ((err= my_init_dynamic_array(&array, sizeof(gtid_pos_element), 0, 0, MYF(0))))
|
|
|
|
goto end;
|
|
|
|
array_inited= true;
|
|
|
|
|
2017-03-08 13:56:29 +01:00
|
|
|
cb_data.hash = &hash;
|
|
|
|
cb_data.array = &array;
|
|
|
|
if ((err= scan_all_gtid_slave_pos_table(thd, load_gtid_state_cb, &cb_data)))
|
2017-03-06 15:32:54 +01:00
|
|
|
goto end;
|
2013-03-18 15:09:36 +01:00
|
|
|
|
2017-03-24 12:07:07 +01:00
|
|
|
if (!cb_data.default_entry)
|
|
|
|
{
|
|
|
|
/*
|
|
|
|
If the mysql.gtid_slave_pos table does not exist, but at least one other
|
|
|
|
table is available, arbitrarily pick the first in the list to use as
|
|
|
|
default.
|
|
|
|
*/
|
|
|
|
cb_data.default_entry= cb_data.table_list;
|
|
|
|
}
|
|
|
|
if ((err= gtid_pos_auto_create_tables(&cb_data.table_list)))
|
|
|
|
goto end;
|
|
|
|
|
2015-11-29 16:51:23 +01:00
|
|
|
mysql_mutex_lock(&rpl_global_gtid_slave_state->LOCK_slave_state);
|
|
|
|
if (rpl_global_gtid_slave_state->loaded)
|
2013-06-03 07:41:38 +02:00
|
|
|
{
|
2015-11-29 16:51:23 +01:00
|
|
|
mysql_mutex_unlock(&rpl_global_gtid_slave_state->LOCK_slave_state);
|
2013-06-03 07:41:38 +02:00
|
|
|
goto end;
|
|
|
|
}
|
2013-06-21 21:23:24 +02:00
|
|
|
|
2017-03-14 12:54:10 +01:00
|
|
|
if (!cb_data.table_list)
|
|
|
|
{
|
|
|
|
my_error(ER_NO_SUCH_TABLE, MYF(0), "mysql",
|
|
|
|
rpl_gtid_slave_state_table_name.str);
|
2017-03-24 12:07:07 +01:00
|
|
|
mysql_mutex_unlock(&rpl_global_gtid_slave_state->LOCK_slave_state);
|
2017-03-14 12:54:10 +01:00
|
|
|
err= 1;
|
|
|
|
goto end;
|
|
|
|
}
|
|
|
|
|
2013-06-21 21:23:24 +02:00
|
|
|
for (i= 0; i < array.elements; ++i)
|
2013-03-18 15:09:36 +01:00
|
|
|
{
|
2013-06-21 21:23:24 +02:00
|
|
|
get_dynamic(&array, (uchar *)&tmp_entry, i);
|
2015-11-29 16:51:23 +01:00
|
|
|
if ((err= rpl_global_gtid_slave_state->update(tmp_entry.gtid.domain_id,
|
2017-03-09 13:27:27 +01:00
|
|
|
tmp_entry.gtid.server_id,
|
|
|
|
tmp_entry.sub_id,
|
|
|
|
tmp_entry.gtid.seq_no,
|
|
|
|
tmp_entry.hton,
|
|
|
|
NULL)))
|
2013-03-18 15:09:36 +01:00
|
|
|
{
|
2015-11-29 16:51:23 +01:00
|
|
|
mysql_mutex_unlock(&rpl_global_gtid_slave_state->LOCK_slave_state);
|
2013-06-03 07:41:38 +02:00
|
|
|
my_error(ER_OUT_OF_RESOURCES, MYF(0));
|
2013-03-18 15:09:36 +01:00
|
|
|
goto end;
|
|
|
|
}
|
2013-06-21 21:23:24 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
for (i= 0; i < hash.records; ++i)
|
|
|
|
{
|
2017-03-06 15:32:54 +01:00
|
|
|
entry= (struct gtid_pos_element *)my_hash_element(&hash, i);
|
2013-05-28 13:28:31 +02:00
|
|
|
if (opt_bin_log &&
|
|
|
|
mysql_bin_log.bump_seq_no_counter_if_needed(entry->gtid.domain_id,
|
|
|
|
entry->gtid.seq_no))
|
|
|
|
{
|
2015-11-29 16:51:23 +01:00
|
|
|
mysql_mutex_unlock(&rpl_global_gtid_slave_state->LOCK_slave_state);
|
2013-06-03 07:41:38 +02:00
|
|
|
my_error(ER_OUT_OF_RESOURCES, MYF(0));
|
2013-05-28 13:28:31 +02:00
|
|
|
goto end;
|
|
|
|
}
|
2013-03-18 15:09:36 +01:00
|
|
|
}
|
2013-06-21 21:23:24 +02:00
|
|
|
|
2017-03-14 12:54:10 +01:00
|
|
|
rpl_global_gtid_slave_state->set_gtid_pos_tables_list(cb_data.table_list,
|
|
|
|
cb_data.default_entry);
|
2017-03-09 12:16:15 +01:00
|
|
|
cb_data.table_list= NULL;
|
2015-11-29 16:51:23 +01:00
|
|
|
rpl_global_gtid_slave_state->loaded= true;
|
|
|
|
mysql_mutex_unlock(&rpl_global_gtid_slave_state->LOCK_slave_state);
|
2013-03-18 15:09:36 +01:00
|
|
|
|
2018-10-14 20:41:49 +02:00
|
|
|
/* Clear out no longer needed elements now. */
|
|
|
|
old_gtids_list=
|
|
|
|
rpl_global_gtid_slave_state->gtid_grab_pending_delete_list();
|
|
|
|
rpl_global_gtid_slave_state->gtid_delete_pending(thd, &old_gtids_list);
|
|
|
|
if (old_gtids_list)
|
|
|
|
rpl_global_gtid_slave_state->put_back_list(old_gtids_list);
|
|
|
|
|
2013-03-18 15:09:36 +01:00
|
|
|
end:
|
2013-06-21 21:23:24 +02:00
|
|
|
if (array_inited)
|
|
|
|
delete_dynamic(&array);
|
2013-03-18 15:09:36 +01:00
|
|
|
my_hash_free(&hash);
|
2017-03-09 12:16:15 +01:00
|
|
|
if (cb_data.table_list)
|
|
|
|
rpl_global_gtid_slave_state->free_gtid_pos_tables(cb_data.table_list);
|
2013-03-18 15:09:36 +01:00
|
|
|
DBUG_RETURN(err);
|
|
|
|
}
|
|
|
|
|
2013-07-03 13:46:33 +02:00
|
|
|
|
2017-03-09 12:16:15 +01:00
|
|
|
static int
|
2017-07-03 10:36:09 +02:00
|
|
|
find_gtid_pos_tables_cb(THD *thd, LEX_CSTRING *table_name, void *arg)
|
2017-03-09 12:16:15 +01:00
|
|
|
{
|
2017-03-14 12:54:10 +01:00
|
|
|
load_gtid_state_cb_data *data= static_cast<load_gtid_state_cb_data *>(arg);
|
2017-03-09 12:16:15 +01:00
|
|
|
TABLE_LIST tlist;
|
|
|
|
TABLE *table= NULL;
|
|
|
|
int err;
|
|
|
|
|
|
|
|
thd->reset_for_next_command();
|
2018-01-07 17:03:44 +01:00
|
|
|
tlist.init_one_table(&MYSQL_SCHEMA_NAME, table_name, NULL, TL_READ);
|
2017-03-09 12:16:15 +01:00
|
|
|
if ((err= open_and_lock_tables(thd, &tlist, FALSE, 0)))
|
|
|
|
goto end;
|
|
|
|
table= tlist.table;
|
|
|
|
|
|
|
|
if ((err= gtid_check_rpl_slave_state_table(table)))
|
|
|
|
goto end;
|
2017-03-14 12:54:10 +01:00
|
|
|
err= process_gtid_pos_table(thd, table_name, table->s->db_type(), data);
|
2017-03-09 12:16:15 +01:00
|
|
|
|
|
|
|
end:
|
|
|
|
if (table)
|
|
|
|
{
|
|
|
|
ha_commit_trans(thd, FALSE);
|
|
|
|
ha_commit_trans(thd, TRUE);
|
|
|
|
close_thread_tables(thd);
|
|
|
|
thd->mdl_context.release_transactional_locks();
|
|
|
|
}
|
|
|
|
|
|
|
|
return err;
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
Re-compute the list of available mysql.gtid_slave_posXXX tables.
|
|
|
|
|
|
|
|
This is done at START SLAVE to pick up any newly created tables without
|
|
|
|
requiring server restart.
|
|
|
|
*/
|
|
|
|
int
|
|
|
|
find_gtid_slave_pos_tables(THD *thd)
|
|
|
|
{
|
|
|
|
int err= 0;
|
2017-03-14 12:54:10 +01:00
|
|
|
load_gtid_state_cb_data cb_data;
|
2017-04-23 10:49:58 +02:00
|
|
|
uint num_running;
|
2017-03-09 12:16:15 +01:00
|
|
|
|
|
|
|
mysql_mutex_lock(&rpl_global_gtid_slave_state->LOCK_slave_state);
|
|
|
|
bool loaded= rpl_global_gtid_slave_state->loaded;
|
|
|
|
mysql_mutex_unlock(&rpl_global_gtid_slave_state->LOCK_slave_state);
|
|
|
|
if (!loaded)
|
|
|
|
return 0;
|
|
|
|
|
2017-03-14 12:54:10 +01:00
|
|
|
cb_data.table_list= NULL;
|
|
|
|
cb_data.default_entry= NULL;
|
|
|
|
if ((err= scan_all_gtid_slave_pos_table(thd, find_gtid_pos_tables_cb, &cb_data)))
|
|
|
|
goto end;
|
|
|
|
|
|
|
|
if (!cb_data.table_list)
|
|
|
|
{
|
|
|
|
my_error(ER_NO_SUCH_TABLE, MYF(0), "mysql",
|
|
|
|
rpl_gtid_slave_state_table_name.str);
|
|
|
|
err= 1;
|
2017-03-09 12:16:15 +01:00
|
|
|
goto end;
|
2017-03-14 12:54:10 +01:00
|
|
|
}
|
2017-03-24 12:07:07 +01:00
|
|
|
if (!cb_data.default_entry)
|
2017-03-14 12:54:10 +01:00
|
|
|
{
|
|
|
|
/*
|
|
|
|
If the mysql.gtid_slave_pos table does not exist, but at least one other
|
|
|
|
table is available, arbitrarily pick the first in the list to use as
|
|
|
|
default.
|
|
|
|
*/
|
|
|
|
cb_data.default_entry= cb_data.table_list;
|
|
|
|
}
|
2017-03-24 12:07:07 +01:00
|
|
|
if ((err= gtid_pos_auto_create_tables(&cb_data.table_list)))
|
|
|
|
goto end;
|
2017-03-09 12:16:15 +01:00
|
|
|
|
2017-04-23 10:49:58 +02:00
|
|
|
mysql_mutex_lock(&LOCK_active_mi);
|
|
|
|
num_running= any_slave_sql_running(true);
|
2017-03-09 12:16:15 +01:00
|
|
|
mysql_mutex_lock(&rpl_global_gtid_slave_state->LOCK_slave_state);
|
2017-04-23 10:49:58 +02:00
|
|
|
if (num_running <= 1)
|
2017-03-14 12:54:10 +01:00
|
|
|
{
|
2017-04-23 10:49:58 +02:00
|
|
|
/*
|
|
|
|
If no slave is running now, the count will be 1, since this SQL thread
|
|
|
|
which is starting is included in the count. In this case, we can safely
|
|
|
|
replace the list, no-one can be trying to read it without lock.
|
|
|
|
*/
|
|
|
|
DBUG_ASSERT(num_running == 1);
|
2017-03-14 12:54:10 +01:00
|
|
|
rpl_global_gtid_slave_state->set_gtid_pos_tables_list(cb_data.table_list,
|
|
|
|
cb_data.default_entry);
|
|
|
|
cb_data.table_list= NULL;
|
|
|
|
}
|
|
|
|
else
|
|
|
|
{
|
|
|
|
/*
|
|
|
|
If there are SQL threads running, we cannot safely remove the old list.
|
|
|
|
However we can add new entries, and warn about any tables that
|
|
|
|
disappeared, but may still be visible to running SQL threads.
|
|
|
|
*/
|
|
|
|
rpl_slave_state::gtid_pos_table *old_entry, *new_entry, **next_ptr_ptr;
|
|
|
|
|
2017-05-10 09:56:31 +02:00
|
|
|
old_entry= (rpl_slave_state::gtid_pos_table *)
|
|
|
|
rpl_global_gtid_slave_state->gtid_pos_tables;
|
2017-03-14 12:54:10 +01:00
|
|
|
while (old_entry)
|
|
|
|
{
|
|
|
|
new_entry= cb_data.table_list;
|
|
|
|
while (new_entry)
|
|
|
|
{
|
|
|
|
if (new_entry->table_hton == old_entry->table_hton)
|
|
|
|
break;
|
|
|
|
new_entry= new_entry->next;
|
|
|
|
}
|
|
|
|
if (!new_entry)
|
|
|
|
sql_print_warning("The table mysql.%s was removed. "
|
|
|
|
"This change will not take full effect "
|
|
|
|
"until all SQL threads have been restarted",
|
|
|
|
old_entry->table_name.str);
|
|
|
|
old_entry= old_entry->next;
|
|
|
|
}
|
|
|
|
next_ptr_ptr= &cb_data.table_list;
|
|
|
|
new_entry= cb_data.table_list;
|
|
|
|
while (new_entry)
|
|
|
|
{
|
|
|
|
/* Check if we already have a table with this storage engine. */
|
2017-05-10 09:56:31 +02:00
|
|
|
old_entry= (rpl_slave_state::gtid_pos_table *)
|
|
|
|
rpl_global_gtid_slave_state->gtid_pos_tables;
|
2017-03-14 12:54:10 +01:00
|
|
|
while (old_entry)
|
|
|
|
{
|
|
|
|
if (new_entry->table_hton == old_entry->table_hton)
|
|
|
|
break;
|
|
|
|
old_entry= old_entry->next;
|
|
|
|
}
|
|
|
|
if (old_entry)
|
|
|
|
{
|
|
|
|
/* This new_entry is already available in the list. */
|
|
|
|
next_ptr_ptr= &new_entry->next;
|
|
|
|
new_entry= new_entry->next;
|
|
|
|
}
|
|
|
|
else
|
|
|
|
{
|
|
|
|
/* Move this new_entry to the list. */
|
|
|
|
rpl_slave_state::gtid_pos_table *next= new_entry->next;
|
|
|
|
rpl_global_gtid_slave_state->add_gtid_pos_table(new_entry);
|
|
|
|
*next_ptr_ptr= next;
|
|
|
|
new_entry= next;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
2017-03-09 12:16:15 +01:00
|
|
|
mysql_mutex_unlock(&rpl_global_gtid_slave_state->LOCK_slave_state);
|
2017-04-23 10:49:58 +02:00
|
|
|
mysql_mutex_unlock(&LOCK_active_mi);
|
2017-03-09 12:16:15 +01:00
|
|
|
|
|
|
|
end:
|
2017-03-14 12:54:10 +01:00
|
|
|
if (cb_data.table_list)
|
|
|
|
rpl_global_gtid_slave_state->free_gtid_pos_tables(cb_data.table_list);
|
2017-03-09 12:16:15 +01:00
|
|
|
return err;
|
|
|
|
}
|
|
|
|
|
|
|
|
|
MDEV-5657: Parallel replication.
Clean up and improve the parallel implementation code, mainly related to
scheduling of work to threads and handling of stop and errors.
Fix a lot of bugs in various corner cases that could lead to crashes or
corruption.
Fix that a single replication domain could easily grab all worker threads and
stall all other domains; now a configuration variable
--slave-domain-parallel-threads allows to limit the number of
workers.
Allow next event group to start as soon as previous group begins the commit
phase (as opposed to when it ends it); this allows multiple event groups on
the slave to participate in group commit, even when no other opportunities for
parallelism are available.
Various fixes:
- Fix some races in the rpl.rpl_parallel test case.
- Fix an old incorrect assertion in Log_event iocache read.
- Fix repeated malloc/free of wait_for_commit and rpl_group_info objects.
- Simplify wait_for_commit wakeup logic.
- Fix one case in queue_for_group_commit() where killing one thread would
fail to correctly signal the error to the next, causing loss of the
transaction after slave restart.
- Fix leaking of pthreads (and their allocated stack) due to missing
PTHREAD_CREATE_DETACHED attribute.
- Fix how one batch of group-committed transactions wait for the previous
batch before starting to execute themselves. The old code had a very
complex scheduling where the first transaction was handled differently,
with subtle bugs in corner cases. Now each event group is always scheduled
for a new worker (in a round-robin fashion amongst available workers).
Keep a count of how many transactions have started to commit, and wait for
that counter to reach the appropriate value.
- Fix slave stop to wait for all workers to actually complete processing;
before, the wait was for update of last_committed_sub_id, which happens a
bit earlier, and could leave worker threads potentially accessing bits of
the replication state that is no longer valid after slave stop.
- Fix a couple of places where the test suite would kill a thread waiting
inside enter_cond() in connection with debug_sync; debug_sync + kill can
crash in rare cases due to a race with mysys_var_current_mutex in this
case.
- Fix some corner cases where we had enter_cond() but no exit_cond().
- Fix that we could get failure in wait_for_prior_commit() but forget to flag
the error with my_error().
- Fix slave stop (both for normal stop and stop due to error). Now, at stop
we pick a specific safe point (in terms of event groups executed) and make
sure that all event groups before that point are executed to completion,
and that no event group after start executing; this ensures a safe place to
restart replication, even for non-transactional stuff/DDL. In error stop,
make sure that all prior event groups are allowed to execute to completion,
and that any later event groups that have started are rolled back, if
possible. The old code could leave eg. T1 and T3 committed but T2 not, or
it could even leave half a transaction not rolled back in some random
worker, which would cause big problems when that worker was later reused
after slave restart.
- Fix the accounting of amount of events queued for one worker. Before, the
amount was reduced immediately as soon as the events were dequeued (which
happens all at once); this allowed twice the amount of events to be queued
in memory for each single worker, which is not what users would expect.
- Fix that an error set during execution of one event was sometimes not
cleared before executing the next, causing problems with the error
reporting.
- Fix incorrect handling of thd->killed in worker threads.
2014-02-26 15:02:09 +01:00
|
|
|
void
|
|
|
|
rpl_group_info::reinit(Relay_log_info *rli)
|
|
|
|
{
|
|
|
|
this->rli= rli;
|
|
|
|
tables_to_lock= NULL;
|
|
|
|
tables_to_lock_count= 0;
|
|
|
|
trans_retries= 0;
|
|
|
|
last_event_start_time= 0;
|
MDEV-5262, MDEV-5914, MDEV-5941, MDEV-6020: Deadlocks during parallel
replication causing replication to fail.
Remove the temporary fix for MDEV-5914, which used READ COMMITTED for parallel
replication worker threads. Replace it with a better, more selective solution.
The issue is with certain edge cases of InnoDB gap locks, for example between
INSERT and ranged DELETE. It is possible for the gap lock set by the DELETE to
block the INSERT, if the DELETE runs first, while the record lock set by
INSERT does not block the DELETE, if the INSERT runs first. This can cause a
conflict between the two in parallel replication on the slave even though they
ran without conflicts on the master.
With this patch, InnoDB will ask the server layer about the two involved
transactions before blocking on a gap lock. If the server layer tells InnoDB
that the transactions are already fixed wrt. commit order, as they are in
parallel replication, InnoDB will ignore the gap lock and allow the two
transactions to proceed in parallel, avoiding the conflict.
Improve the fix for MDEV-6020. When InnoDB itself detects a deadlock, it now
asks the server layer for any preferences about which transaction to roll
back. In case of parallel replication with two transactions T1 and T2 fixed to
commit T1 before T2, the server layer will ask InnoDB to roll back T2 as the
deadlock victim, not T1. This helps in some cases to avoid excessive deadlock
rollback, as T2 will in any case need to wait for T1 to complete before it can
itself commit.
Also some misc. fixes found during development and testing:
- Remove thd_rpl_is_parallel(), it is not used or needed.
- Use KILL_CONNECTION instead of KILL_QUERY when a parallel replication
worker thread is killed to resolve a deadlock with fixed commit
ordering. There are some cases, eg. in sql/sql_parse.cc, where a KILL_QUERY
can be ignored if the query otherwise completed successfully, and this
could cause the deadlock kill to be lost, so that the deadlock was not
correctly resolved.
- Fix random test failure due to missing wait_for_binlog_checkpoint.inc.
- Make sure that deadlock or other temporary errors during parallel
replication are not printed to the the error log; there were some places
around the replication code with extra error logging. These conditions can
occur occasionally and are handled automatically without breaking
replication, so they should not pollute the error log.
- Fix handling of rgi->gtid_sub_id. We need to be able to access this also at
the end of a transaction, to be able to detect and resolve deadlocks due to
commit ordering. But this value was also used as a flag to mark whether
record_gtid() had been called, by being set to zero, losing the value. Now,
introduce a separate flag rgi->gtid_pending, so rgi->gtid_sub_id remains
valid for the entire duration of the transaction.
- Fix one place where the code to handle ignored errors called reset_killed()
unconditionally, even if no error was caught that should be ignored. This
could cause loss of a deadlock kill signal, breaking deadlock detection and
resolution.
- Fix a couple of missing mysql_reset_thd_for_next_command(). This could
cause a prior error condition to remain for the next event executed,
causing assertions about errors already being set and possibly giving
incorrect error handling for following event executions.
- Fix code that cleared thd->rgi_slave in the parallel replication worker
threads after each event execution; this caused the deadlock detection and
handling code to not be able to correctly process the associated
transactions as belonging to replication worker threads.
- Remove useless error code in slave_background_kill_request().
- Fix bug where wfc->wakeup_error was not cleared at
wait_for_commit::unregister_wait_for_prior_commit(). This could cause the
error condition to wrongly propagate to a later wait_for_prior_commit(),
causing spurious ER_PRIOR_COMMIT_FAILED errors.
- Do not put the binlog background thread into the processlist. It causes
too many result differences in mtr, but also it probably is not useful
for users to pollute the process list with a system thread that does not
really perform any user-visible tasks...
2014-06-10 10:13:15 +02:00
|
|
|
gtid_sub_id= 0;
|
2014-07-08 12:54:47 +02:00
|
|
|
commit_id= 0;
|
MDEV-5262, MDEV-5914, MDEV-5941, MDEV-6020: Deadlocks during parallel
replication causing replication to fail.
Remove the temporary fix for MDEV-5914, which used READ COMMITTED for parallel
replication worker threads. Replace it with a better, more selective solution.
The issue is with certain edge cases of InnoDB gap locks, for example between
INSERT and ranged DELETE. It is possible for the gap lock set by the DELETE to
block the INSERT, if the DELETE runs first, while the record lock set by
INSERT does not block the DELETE, if the INSERT runs first. This can cause a
conflict between the two in parallel replication on the slave even though they
ran without conflicts on the master.
With this patch, InnoDB will ask the server layer about the two involved
transactions before blocking on a gap lock. If the server layer tells InnoDB
that the transactions are already fixed wrt. commit order, as they are in
parallel replication, InnoDB will ignore the gap lock and allow the two
transactions to proceed in parallel, avoiding the conflict.
Improve the fix for MDEV-6020. When InnoDB itself detects a deadlock, it now
asks the server layer for any preferences about which transaction to roll
back. In case of parallel replication with two transactions T1 and T2 fixed to
commit T1 before T2, the server layer will ask InnoDB to roll back T2 as the
deadlock victim, not T1. This helps in some cases to avoid excessive deadlock
rollback, as T2 will in any case need to wait for T1 to complete before it can
itself commit.
Also some misc. fixes found during development and testing:
- Remove thd_rpl_is_parallel(), it is not used or needed.
- Use KILL_CONNECTION instead of KILL_QUERY when a parallel replication
worker thread is killed to resolve a deadlock with fixed commit
ordering. There are some cases, eg. in sql/sql_parse.cc, where a KILL_QUERY
can be ignored if the query otherwise completed successfully, and this
could cause the deadlock kill to be lost, so that the deadlock was not
correctly resolved.
- Fix random test failure due to missing wait_for_binlog_checkpoint.inc.
- Make sure that deadlock or other temporary errors during parallel
replication are not printed to the the error log; there were some places
around the replication code with extra error logging. These conditions can
occur occasionally and are handled automatically without breaking
replication, so they should not pollute the error log.
- Fix handling of rgi->gtid_sub_id. We need to be able to access this also at
the end of a transaction, to be able to detect and resolve deadlocks due to
commit ordering. But this value was also used as a flag to mark whether
record_gtid() had been called, by being set to zero, losing the value. Now,
introduce a separate flag rgi->gtid_pending, so rgi->gtid_sub_id remains
valid for the entire duration of the transaction.
- Fix one place where the code to handle ignored errors called reset_killed()
unconditionally, even if no error was caught that should be ignored. This
could cause loss of a deadlock kill signal, breaking deadlock detection and
resolution.
- Fix a couple of missing mysql_reset_thd_for_next_command(). This could
cause a prior error condition to remain for the next event executed,
causing assertions about errors already being set and possibly giving
incorrect error handling for following event executions.
- Fix code that cleared thd->rgi_slave in the parallel replication worker
threads after each event execution; this caused the deadlock detection and
handling code to not be able to correctly process the associated
transactions as belonging to replication worker threads.
- Remove useless error code in slave_background_kill_request().
- Fix bug where wfc->wakeup_error was not cleared at
wait_for_commit::unregister_wait_for_prior_commit(). This could cause the
error condition to wrongly propagate to a later wait_for_prior_commit(),
causing spurious ER_PRIOR_COMMIT_FAILED errors.
- Do not put the binlog background thread into the processlist. It causes
too many result differences in mtr, but also it probably is not useful
for users to pollute the process list with a system thread that does not
really perform any user-visible tasks...
2014-06-10 10:13:15 +02:00
|
|
|
gtid_pending= false;
|
2014-03-21 10:11:28 +01:00
|
|
|
worker_error= 0;
|
MDEV-5657: Parallel replication.
Clean up and improve the parallel implementation code, mainly related to
scheduling of work to threads and handling of stop and errors.
Fix a lot of bugs in various corner cases that could lead to crashes or
corruption.
Fix that a single replication domain could easily grab all worker threads and
stall all other domains; now a configuration variable
--slave-domain-parallel-threads allows to limit the number of
workers.
Allow next event group to start as soon as previous group begins the commit
phase (as opposed to when it ends it); this allows multiple event groups on
the slave to participate in group commit, even when no other opportunities for
parallelism are available.
Various fixes:
- Fix some races in the rpl.rpl_parallel test case.
- Fix an old incorrect assertion in Log_event iocache read.
- Fix repeated malloc/free of wait_for_commit and rpl_group_info objects.
- Simplify wait_for_commit wakeup logic.
- Fix one case in queue_for_group_commit() where killing one thread would
fail to correctly signal the error to the next, causing loss of the
transaction after slave restart.
- Fix leaking of pthreads (and their allocated stack) due to missing
PTHREAD_CREATE_DETACHED attribute.
- Fix how one batch of group-committed transactions wait for the previous
batch before starting to execute themselves. The old code had a very
complex scheduling where the first transaction was handled differently,
with subtle bugs in corner cases. Now each event group is always scheduled
for a new worker (in a round-robin fashion amongst available workers).
Keep a count of how many transactions have started to commit, and wait for
that counter to reach the appropriate value.
- Fix slave stop to wait for all workers to actually complete processing;
before, the wait was for update of last_committed_sub_id, which happens a
bit earlier, and could leave worker threads potentially accessing bits of
the replication state that is no longer valid after slave stop.
- Fix a couple of places where the test suite would kill a thread waiting
inside enter_cond() in connection with debug_sync; debug_sync + kill can
crash in rare cases due to a race with mysys_var_current_mutex in this
case.
- Fix some corner cases where we had enter_cond() but no exit_cond().
- Fix that we could get failure in wait_for_prior_commit() but forget to flag
the error with my_error().
- Fix slave stop (both for normal stop and stop due to error). Now, at stop
we pick a specific safe point (in terms of event groups executed) and make
sure that all event groups before that point are executed to completion,
and that no event group after start executing; this ensures a safe place to
restart replication, even for non-transactional stuff/DDL. In error stop,
make sure that all prior event groups are allowed to execute to completion,
and that any later event groups that have started are rolled back, if
possible. The old code could leave eg. T1 and T3 committed but T2 not, or
it could even leave half a transaction not rolled back in some random
worker, which would cause big problems when that worker was later reused
after slave restart.
- Fix the accounting of amount of events queued for one worker. Before, the
amount was reduced immediately as soon as the events were dequeued (which
happens all at once); this allowed twice the amount of events to be queued
in memory for each single worker, which is not what users would expect.
- Fix that an error set during execution of one event was sometimes not
cleared before executing the next, causing problems with the error
reporting.
- Fix incorrect handling of thd->killed in worker threads.
2014-02-26 15:02:09 +01:00
|
|
|
row_stmt_start_timestamp= 0;
|
|
|
|
long_find_row_note_printed= false;
|
|
|
|
did_mark_start_commit= false;
|
2014-12-05 16:09:48 +01:00
|
|
|
gtid_ev_flags2= 0;
|
2015-10-22 10:28:51 +02:00
|
|
|
last_master_timestamp = 0;
|
2014-03-12 00:14:49 +01:00
|
|
|
gtid_ignore_duplicate_state= GTID_DUPLICATE_NULL;
|
2014-12-05 16:09:48 +01:00
|
|
|
speculation= SPECULATE_NO;
|
MDEV-5657: Parallel replication.
Clean up and improve the parallel implementation code, mainly related to
scheduling of work to threads and handling of stop and errors.
Fix a lot of bugs in various corner cases that could lead to crashes or
corruption.
Fix that a single replication domain could easily grab all worker threads and
stall all other domains; now a configuration variable
--slave-domain-parallel-threads allows to limit the number of
workers.
Allow next event group to start as soon as previous group begins the commit
phase (as opposed to when it ends it); this allows multiple event groups on
the slave to participate in group commit, even when no other opportunities for
parallelism are available.
Various fixes:
- Fix some races in the rpl.rpl_parallel test case.
- Fix an old incorrect assertion in Log_event iocache read.
- Fix repeated malloc/free of wait_for_commit and rpl_group_info objects.
- Simplify wait_for_commit wakeup logic.
- Fix one case in queue_for_group_commit() where killing one thread would
fail to correctly signal the error to the next, causing loss of the
transaction after slave restart.
- Fix leaking of pthreads (and their allocated stack) due to missing
PTHREAD_CREATE_DETACHED attribute.
- Fix how one batch of group-committed transactions wait for the previous
batch before starting to execute themselves. The old code had a very
complex scheduling where the first transaction was handled differently,
with subtle bugs in corner cases. Now each event group is always scheduled
for a new worker (in a round-robin fashion amongst available workers).
Keep a count of how many transactions have started to commit, and wait for
that counter to reach the appropriate value.
- Fix slave stop to wait for all workers to actually complete processing;
before, the wait was for update of last_committed_sub_id, which happens a
bit earlier, and could leave worker threads potentially accessing bits of
the replication state that is no longer valid after slave stop.
- Fix a couple of places where the test suite would kill a thread waiting
inside enter_cond() in connection with debug_sync; debug_sync + kill can
crash in rare cases due to a race with mysys_var_current_mutex in this
case.
- Fix some corner cases where we had enter_cond() but no exit_cond().
- Fix that we could get failure in wait_for_prior_commit() but forget to flag
the error with my_error().
- Fix slave stop (both for normal stop and stop due to error). Now, at stop
we pick a specific safe point (in terms of event groups executed) and make
sure that all event groups before that point are executed to completion,
and that no event group after start executing; this ensures a safe place to
restart replication, even for non-transactional stuff/DDL. In error stop,
make sure that all prior event groups are allowed to execute to completion,
and that any later event groups that have started are rolled back, if
possible. The old code could leave eg. T1 and T3 committed but T2 not, or
it could even leave half a transaction not rolled back in some random
worker, which would cause big problems when that worker was later reused
after slave restart.
- Fix the accounting of amount of events queued for one worker. Before, the
amount was reduced immediately as soon as the events were dequeued (which
happens all at once); this allowed twice the amount of events to be queued
in memory for each single worker, which is not what users would expect.
- Fix that an error set during execution of one event was sometimes not
cleared before executing the next, causing problems with the error
reporting.
- Fix incorrect handling of thd->killed in worker threads.
2014-02-26 15:02:09 +01:00
|
|
|
commit_orderer.reinit();
|
|
|
|
}
|
|
|
|
|
|
|
|
rpl_group_info::rpl_group_info(Relay_log_info *rli)
|
MDEV-5262, MDEV-5914, MDEV-5941, MDEV-6020: Deadlocks during parallel
replication causing replication to fail.
Remove the temporary fix for MDEV-5914, which used READ COMMITTED for parallel
replication worker threads. Replace it with a better, more selective solution.
The issue is with certain edge cases of InnoDB gap locks, for example between
INSERT and ranged DELETE. It is possible for the gap lock set by the DELETE to
block the INSERT, if the DELETE runs first, while the record lock set by
INSERT does not block the DELETE, if the INSERT runs first. This can cause a
conflict between the two in parallel replication on the slave even though they
ran without conflicts on the master.
With this patch, InnoDB will ask the server layer about the two involved
transactions before blocking on a gap lock. If the server layer tells InnoDB
that the transactions are already fixed wrt. commit order, as they are in
parallel replication, InnoDB will ignore the gap lock and allow the two
transactions to proceed in parallel, avoiding the conflict.
Improve the fix for MDEV-6020. When InnoDB itself detects a deadlock, it now
asks the server layer for any preferences about which transaction to roll
back. In case of parallel replication with two transactions T1 and T2 fixed to
commit T1 before T2, the server layer will ask InnoDB to roll back T2 as the
deadlock victim, not T1. This helps in some cases to avoid excessive deadlock
rollback, as T2 will in any case need to wait for T1 to complete before it can
itself commit.
Also some misc. fixes found during development and testing:
- Remove thd_rpl_is_parallel(), it is not used or needed.
- Use KILL_CONNECTION instead of KILL_QUERY when a parallel replication
worker thread is killed to resolve a deadlock with fixed commit
ordering. There are some cases, eg. in sql/sql_parse.cc, where a KILL_QUERY
can be ignored if the query otherwise completed successfully, and this
could cause the deadlock kill to be lost, so that the deadlock was not
correctly resolved.
- Fix random test failure due to missing wait_for_binlog_checkpoint.inc.
- Make sure that deadlock or other temporary errors during parallel
replication are not printed to the the error log; there were some places
around the replication code with extra error logging. These conditions can
occur occasionally and are handled automatically without breaking
replication, so they should not pollute the error log.
- Fix handling of rgi->gtid_sub_id. We need to be able to access this also at
the end of a transaction, to be able to detect and resolve deadlocks due to
commit ordering. But this value was also used as a flag to mark whether
record_gtid() had been called, by being set to zero, losing the value. Now,
introduce a separate flag rgi->gtid_pending, so rgi->gtid_sub_id remains
valid for the entire duration of the transaction.
- Fix one place where the code to handle ignored errors called reset_killed()
unconditionally, even if no error was caught that should be ignored. This
could cause loss of a deadlock kill signal, breaking deadlock detection and
resolution.
- Fix a couple of missing mysql_reset_thd_for_next_command(). This could
cause a prior error condition to remain for the next event executed,
causing assertions about errors already being set and possibly giving
incorrect error handling for following event executions.
- Fix code that cleared thd->rgi_slave in the parallel replication worker
threads after each event execution; this caused the deadlock detection and
handling code to not be able to correctly process the associated
transactions as belonging to replication worker threads.
- Remove useless error code in slave_background_kill_request().
- Fix bug where wfc->wakeup_error was not cleared at
wait_for_commit::unregister_wait_for_prior_commit(). This could cause the
error condition to wrongly propagate to a later wait_for_prior_commit(),
causing spurious ER_PRIOR_COMMIT_FAILED errors.
- Do not put the binlog background thread into the processlist. It causes
too many result differences in mtr, but also it probably is not useful
for users to pollute the process list with a system thread that does not
really perform any user-visible tasks...
2014-06-10 10:13:15 +02:00
|
|
|
: thd(0), wait_commit_sub_id(0),
|
MDEV-5657: Parallel replication.
Clean up and improve the parallel implementation code, mainly related to
scheduling of work to threads and handling of stop and errors.
Fix a lot of bugs in various corner cases that could lead to crashes or
corruption.
Fix that a single replication domain could easily grab all worker threads and
stall all other domains; now a configuration variable
--slave-domain-parallel-threads allows to limit the number of
workers.
Allow next event group to start as soon as previous group begins the commit
phase (as opposed to when it ends it); this allows multiple event groups on
the slave to participate in group commit, even when no other opportunities for
parallelism are available.
Various fixes:
- Fix some races in the rpl.rpl_parallel test case.
- Fix an old incorrect assertion in Log_event iocache read.
- Fix repeated malloc/free of wait_for_commit and rpl_group_info objects.
- Simplify wait_for_commit wakeup logic.
- Fix one case in queue_for_group_commit() where killing one thread would
fail to correctly signal the error to the next, causing loss of the
transaction after slave restart.
- Fix leaking of pthreads (and their allocated stack) due to missing
PTHREAD_CREATE_DETACHED attribute.
- Fix how one batch of group-committed transactions wait for the previous
batch before starting to execute themselves. The old code had a very
complex scheduling where the first transaction was handled differently,
with subtle bugs in corner cases. Now each event group is always scheduled
for a new worker (in a round-robin fashion amongst available workers).
Keep a count of how many transactions have started to commit, and wait for
that counter to reach the appropriate value.
- Fix slave stop to wait for all workers to actually complete processing;
before, the wait was for update of last_committed_sub_id, which happens a
bit earlier, and could leave worker threads potentially accessing bits of
the replication state that is no longer valid after slave stop.
- Fix a couple of places where the test suite would kill a thread waiting
inside enter_cond() in connection with debug_sync; debug_sync + kill can
crash in rare cases due to a race with mysys_var_current_mutex in this
case.
- Fix some corner cases where we had enter_cond() but no exit_cond().
- Fix that we could get failure in wait_for_prior_commit() but forget to flag
the error with my_error().
- Fix slave stop (both for normal stop and stop due to error). Now, at stop
we pick a specific safe point (in terms of event groups executed) and make
sure that all event groups before that point are executed to completion,
and that no event group after start executing; this ensures a safe place to
restart replication, even for non-transactional stuff/DDL. In error stop,
make sure that all prior event groups are allowed to execute to completion,
and that any later event groups that have started are rolled back, if
possible. The old code could leave eg. T1 and T3 committed but T2 not, or
it could even leave half a transaction not rolled back in some random
worker, which would cause big problems when that worker was later reused
after slave restart.
- Fix the accounting of amount of events queued for one worker. Before, the
amount was reduced immediately as soon as the events were dequeued (which
happens all at once); this allowed twice the amount of events to be queued
in memory for each single worker, which is not what users would expect.
- Fix that an error set during execution of one event was sometimes not
cleared before executing the next, causing problems with the error
reporting.
- Fix incorrect handling of thd->killed in worker threads.
2014-02-26 15:02:09 +01:00
|
|
|
wait_commit_group_info(0), parallel_entry(0),
|
|
|
|
deferred_events(NULL), m_annotate_event(0), is_parallel_exec(false)
|
2013-07-03 13:46:33 +02:00
|
|
|
{
|
MDEV-5657: Parallel replication.
Clean up and improve the parallel implementation code, mainly related to
scheduling of work to threads and handling of stop and errors.
Fix a lot of bugs in various corner cases that could lead to crashes or
corruption.
Fix that a single replication domain could easily grab all worker threads and
stall all other domains; now a configuration variable
--slave-domain-parallel-threads allows to limit the number of
workers.
Allow next event group to start as soon as previous group begins the commit
phase (as opposed to when it ends it); this allows multiple event groups on
the slave to participate in group commit, even when no other opportunities for
parallelism are available.
Various fixes:
- Fix some races in the rpl.rpl_parallel test case.
- Fix an old incorrect assertion in Log_event iocache read.
- Fix repeated malloc/free of wait_for_commit and rpl_group_info objects.
- Simplify wait_for_commit wakeup logic.
- Fix one case in queue_for_group_commit() where killing one thread would
fail to correctly signal the error to the next, causing loss of the
transaction after slave restart.
- Fix leaking of pthreads (and their allocated stack) due to missing
PTHREAD_CREATE_DETACHED attribute.
- Fix how one batch of group-committed transactions wait for the previous
batch before starting to execute themselves. The old code had a very
complex scheduling where the first transaction was handled differently,
with subtle bugs in corner cases. Now each event group is always scheduled
for a new worker (in a round-robin fashion amongst available workers).
Keep a count of how many transactions have started to commit, and wait for
that counter to reach the appropriate value.
- Fix slave stop to wait for all workers to actually complete processing;
before, the wait was for update of last_committed_sub_id, which happens a
bit earlier, and could leave worker threads potentially accessing bits of
the replication state that is no longer valid after slave stop.
- Fix a couple of places where the test suite would kill a thread waiting
inside enter_cond() in connection with debug_sync; debug_sync + kill can
crash in rare cases due to a race with mysys_var_current_mutex in this
case.
- Fix some corner cases where we had enter_cond() but no exit_cond().
- Fix that we could get failure in wait_for_prior_commit() but forget to flag
the error with my_error().
- Fix slave stop (both for normal stop and stop due to error). Now, at stop
we pick a specific safe point (in terms of event groups executed) and make
sure that all event groups before that point are executed to completion,
and that no event group after start executing; this ensures a safe place to
restart replication, even for non-transactional stuff/DDL. In error stop,
make sure that all prior event groups are allowed to execute to completion,
and that any later event groups that have started are rolled back, if
possible. The old code could leave eg. T1 and T3 committed but T2 not, or
it could even leave half a transaction not rolled back in some random
worker, which would cause big problems when that worker was later reused
after slave restart.
- Fix the accounting of amount of events queued for one worker. Before, the
amount was reduced immediately as soon as the events were dequeued (which
happens all at once); this allowed twice the amount of events to be queued
in memory for each single worker, which is not what users would expect.
- Fix that an error set during execution of one event was sometimes not
cleared before executing the next, causing problems with the error
reporting.
- Fix incorrect handling of thd->killed in worker threads.
2014-02-26 15:02:09 +01:00
|
|
|
reinit(rli);
|
2013-07-03 13:46:33 +02:00
|
|
|
bzero(¤t_gtid, sizeof(current_gtid));
|
Fixes for parallel slave:
- Made slaves temporary table multi-thread slave safe by adding mutex around save_temporary_table usage.
- rli->save_temporary_tables is the active list of all used temporary tables
- This is copied to THD->temporary_tables when temporary tables are opened and updated when temporary tables are closed
- Added THD->lock_temporary_tables() and THD->unlock_temporary_tables() to simplify this.
- Relay_log_info->sql_thd renamed to Relay_log_info->sql_driver_thd to avoid wrong usage for merged code.
- Added is_part_of_group() to mark functions that are part of the next function. This replaces setting IN_STMT when events are executed.
- Added is_begin(), is_commit() and is_rollback() functions to Query_log_event to simplify code.
- If slave_skip_counter is set run things in single threaded mode. This simplifies code for skipping events.
- Updating state of relay log (IN_STMT and IN_TRANSACTION) is moved to one single function: update_state_of_relay_log()
We can't use OPTION_BEGIN to check for the state anymore as the sql_driver and sql execution threads may be different.
Clear IN_STMT and IN_TRANSACTION in init_relay_log_pos() and Relay_log_info::cleanup_context() to ensure the flags doesn't survive slave restarts
is_in_group() is now independent of state of executed transaction.
- Reset thd->transaction.all.modified_non_trans_table() if we did set it for single table row events.
This was mainly for keeping the flag as documented.
- Changed slave_open_temp_tables to uint32 to be able to use atomic operators on it.
- Relay_log_info::sleep_lock -> rpl_group_info::sleep_lock
- Relay_log_info::sleep_cond -> rpl_group_info::sleep_cond
- Changed some functions to take rpl_group_info instead of Relay_log_info to make them multi-slave safe and to simplify usage
- do_shall_skip()
- continue_group()
- sql_slave_killed()
- next_event()
- Simplifed arguments to io_salve_killed(), check_io_slave_killed() and sql_slave_killed(); No reason to supply THD as this is part of the given structure.
- set_thd_in_use_temporary_tables() removed as in_use is set on usage
- Added information to thd_proc_info() which thread is waiting for slave mutex to exit.
- In open_table() reuse code from find_temporary_table()
Other things:
- More DBUG statements
- Fixed the rpl_incident.test can be run with --debug
- More comments
- Disabled not used function rpl_connect_master()
mysql-test/suite/perfschema/r/all_instances.result:
Moved sleep_lock and sleep_cond to rpl_group_info
mysql-test/suite/rpl/r/rpl_incident.result:
Updated result
mysql-test/suite/rpl/t/rpl_incident-master.opt:
Not needed anymore
mysql-test/suite/rpl/t/rpl_incident.test:
Fixed that test can be run with --debug
sql/handler.cc:
More DBUG_PRINT
sql/log.cc:
More comments
sql/log_event.cc:
Added DBUG statements
do_shall_skip(), continue_group() now takes rpl_group_info param
Use is_begin(), is_commit() and is_rollback() functions instead of inspecting query string
We don't have set slaves temporary tables 'in_use' as this is now done when tables are opened.
Removed IN_STMT flag setting. This is now done in update_state_of_relay_log()
Use IN_TRANSACTION flag to test state of relay log.
In rows_event_stmt_cleanup() reset thd->transaction.all.modified_non_trans_table if we had set this before.
sql/log_event.h:
do_shall_skip(), continue_group() now takes rpl_group_info param
Added is_part_of_group() to mark events that are part of the next event. This replaces setting IN_STMT when events are executed.
Added is_begin(), is_commit() and is_rollback() functions to Query_log_event to simplify code.
sql/log_event_old.cc:
Removed IN_STMT flag setting. This is now done in update_state_of_relay_log()
do_shall_skip(), continue_group() now takes rpl_group_info param
sql/log_event_old.h:
Added is_part_of_group() to mark events that are part of the next event.
do_shall_skip(), continue_group() now takes rpl_group_info param
sql/mysqld.cc:
Changed slave_open_temp_tables to uint32 to be able to use atomic operators on it.
Relay_log_info::sleep_lock -> Rpl_group_info::sleep_lock
Relay_log_info::sleep_cond -> Rpl_group_info::sleep_cond
sql/mysqld.h:
Updated types and names
sql/rpl_gtid.cc:
More DBUG
sql/rpl_parallel.cc:
Updated TODO section
Set thd for event that is execution
Use new is_begin(), is_commit() and is_rollback() functions.
More comments
sql/rpl_rli.cc:
sql_thd -> sql_driver_thd
Relay_log_info::sleep_lock -> rpl_group_info::sleep_lock
Relay_log_info::sleep_cond -> rpl_group_info::sleep_cond
Clear IN_STMT and IN_TRANSACTION in init_relay_log_pos() and Relay_log_info::cleanup_context() to ensure the flags doesn't survive slave restarts.
Reset table->in_use for temporary tables as the table may have been used by another THD.
Use IN_TRANSACTION instead of OPTION_BEGIN to check state of relay log.
Removed IN_STMT flag setting. This is now done in update_state_of_relay_log()
sql/rpl_rli.h:
Changed relay log state flags to bit masks instead of bit positions (most other code we have uses bit masks)
Added IN_TRANSACTION to mark if we are in a BEGIN ... COMMIT section.
save_temporary_tables is now thread safe
Relay_log_info::sleep_lock -> rpl_group_info::sleep_lock
Relay_log_info::sleep_cond -> rpl_group_info::sleep_cond
Relay_log_info->sql_thd renamed to Relay_log_info->sql_driver_thd to avoid wrong usage for merged code
is_in_group() is now independent of state of executed transaction.
sql/slave.cc:
Simplifed arguments to io_salve_killed(), sql_slave_killed() and check_io_slave_killed(); No reason to supply THD as this is part of the given structure.
set_thd_in_use_temporary_tables() removed as in_use is set on usage in sql_base.cc
sql_thd -> sql_driver_thd
More DBUG
Added update_state_of_relay_log() which will calculate the IN_STMT and IN_TRANSACTION state of the relay log after the current element is executed.
If slave_skip_counter is set run things in single threaded mode.
Simplifed arguments to io_salve_killed(), check_io_slave_killed() and sql_slave_killed(); No reason to supply THD as this is part of the given structure.
Added information to thd_proc_info() which thread is waiting for slave mutex to exit.
Disabled not used function rpl_connect_master()
Updated argument to next_event()
sql/sql_base.cc:
Added mutex around usage of slave's temporary tables. The active list is always kept up to date in sql->rgi_slave->save_temporary_tables.
Clear thd->temporary_tables after query (safety)
More DBUG
When using temporary table, set table->in_use to current thd as the THD may be different for slave threads.
Some code is ifdef:ed with REMOVE_AFTER_MERGE_WITH_10 as the given code in 10.0 is not yet in this tree.
In open_table() reuse code from find_temporary_table()
sql/sql_binlog.cc:
rli->sql_thd -> rli->sql_driver_thd
Remove duplicate setting of rgi->rli
sql/sql_class.cc:
Added helper functions rgi_lock_temporary_tables() and rgi_unlock_temporary_tables()
Would have been nicer to have these inline, but there was no easy way to do that
sql/sql_class.h:
Added functions to protect slaves temporary tables
sql/sql_parse.cc:
Added DBUG_PRINT
sql/transaction.cc:
Added comment
2013-10-13 23:24:05 +02:00
|
|
|
mysql_mutex_init(key_rpl_group_info_sleep_lock, &sleep_lock,
|
|
|
|
MY_MUTEX_INIT_FAST);
|
|
|
|
mysql_cond_init(key_rpl_group_info_sleep_cond, &sleep_cond, NULL);
|
2013-07-03 13:46:33 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
|
2013-07-12 14:52:05 +02:00
|
|
|
rpl_group_info::~rpl_group_info()
|
|
|
|
{
|
|
|
|
free_annotate_event();
|
2013-11-08 15:14:18 +01:00
|
|
|
delete deferred_events;
|
Fixes for parallel slave:
- Made slaves temporary table multi-thread slave safe by adding mutex around save_temporary_table usage.
- rli->save_temporary_tables is the active list of all used temporary tables
- This is copied to THD->temporary_tables when temporary tables are opened and updated when temporary tables are closed
- Added THD->lock_temporary_tables() and THD->unlock_temporary_tables() to simplify this.
- Relay_log_info->sql_thd renamed to Relay_log_info->sql_driver_thd to avoid wrong usage for merged code.
- Added is_part_of_group() to mark functions that are part of the next function. This replaces setting IN_STMT when events are executed.
- Added is_begin(), is_commit() and is_rollback() functions to Query_log_event to simplify code.
- If slave_skip_counter is set run things in single threaded mode. This simplifies code for skipping events.
- Updating state of relay log (IN_STMT and IN_TRANSACTION) is moved to one single function: update_state_of_relay_log()
We can't use OPTION_BEGIN to check for the state anymore as the sql_driver and sql execution threads may be different.
Clear IN_STMT and IN_TRANSACTION in init_relay_log_pos() and Relay_log_info::cleanup_context() to ensure the flags doesn't survive slave restarts
is_in_group() is now independent of state of executed transaction.
- Reset thd->transaction.all.modified_non_trans_table() if we did set it for single table row events.
This was mainly for keeping the flag as documented.
- Changed slave_open_temp_tables to uint32 to be able to use atomic operators on it.
- Relay_log_info::sleep_lock -> rpl_group_info::sleep_lock
- Relay_log_info::sleep_cond -> rpl_group_info::sleep_cond
- Changed some functions to take rpl_group_info instead of Relay_log_info to make them multi-slave safe and to simplify usage
- do_shall_skip()
- continue_group()
- sql_slave_killed()
- next_event()
- Simplifed arguments to io_salve_killed(), check_io_slave_killed() and sql_slave_killed(); No reason to supply THD as this is part of the given structure.
- set_thd_in_use_temporary_tables() removed as in_use is set on usage
- Added information to thd_proc_info() which thread is waiting for slave mutex to exit.
- In open_table() reuse code from find_temporary_table()
Other things:
- More DBUG statements
- Fixed the rpl_incident.test can be run with --debug
- More comments
- Disabled not used function rpl_connect_master()
mysql-test/suite/perfschema/r/all_instances.result:
Moved sleep_lock and sleep_cond to rpl_group_info
mysql-test/suite/rpl/r/rpl_incident.result:
Updated result
mysql-test/suite/rpl/t/rpl_incident-master.opt:
Not needed anymore
mysql-test/suite/rpl/t/rpl_incident.test:
Fixed that test can be run with --debug
sql/handler.cc:
More DBUG_PRINT
sql/log.cc:
More comments
sql/log_event.cc:
Added DBUG statements
do_shall_skip(), continue_group() now takes rpl_group_info param
Use is_begin(), is_commit() and is_rollback() functions instead of inspecting query string
We don't have set slaves temporary tables 'in_use' as this is now done when tables are opened.
Removed IN_STMT flag setting. This is now done in update_state_of_relay_log()
Use IN_TRANSACTION flag to test state of relay log.
In rows_event_stmt_cleanup() reset thd->transaction.all.modified_non_trans_table if we had set this before.
sql/log_event.h:
do_shall_skip(), continue_group() now takes rpl_group_info param
Added is_part_of_group() to mark events that are part of the next event. This replaces setting IN_STMT when events are executed.
Added is_begin(), is_commit() and is_rollback() functions to Query_log_event to simplify code.
sql/log_event_old.cc:
Removed IN_STMT flag setting. This is now done in update_state_of_relay_log()
do_shall_skip(), continue_group() now takes rpl_group_info param
sql/log_event_old.h:
Added is_part_of_group() to mark events that are part of the next event.
do_shall_skip(), continue_group() now takes rpl_group_info param
sql/mysqld.cc:
Changed slave_open_temp_tables to uint32 to be able to use atomic operators on it.
Relay_log_info::sleep_lock -> Rpl_group_info::sleep_lock
Relay_log_info::sleep_cond -> Rpl_group_info::sleep_cond
sql/mysqld.h:
Updated types and names
sql/rpl_gtid.cc:
More DBUG
sql/rpl_parallel.cc:
Updated TODO section
Set thd for event that is execution
Use new is_begin(), is_commit() and is_rollback() functions.
More comments
sql/rpl_rli.cc:
sql_thd -> sql_driver_thd
Relay_log_info::sleep_lock -> rpl_group_info::sleep_lock
Relay_log_info::sleep_cond -> rpl_group_info::sleep_cond
Clear IN_STMT and IN_TRANSACTION in init_relay_log_pos() and Relay_log_info::cleanup_context() to ensure the flags doesn't survive slave restarts.
Reset table->in_use for temporary tables as the table may have been used by another THD.
Use IN_TRANSACTION instead of OPTION_BEGIN to check state of relay log.
Removed IN_STMT flag setting. This is now done in update_state_of_relay_log()
sql/rpl_rli.h:
Changed relay log state flags to bit masks instead of bit positions (most other code we have uses bit masks)
Added IN_TRANSACTION to mark if we are in a BEGIN ... COMMIT section.
save_temporary_tables is now thread safe
Relay_log_info::sleep_lock -> rpl_group_info::sleep_lock
Relay_log_info::sleep_cond -> rpl_group_info::sleep_cond
Relay_log_info->sql_thd renamed to Relay_log_info->sql_driver_thd to avoid wrong usage for merged code
is_in_group() is now independent of state of executed transaction.
sql/slave.cc:
Simplifed arguments to io_salve_killed(), sql_slave_killed() and check_io_slave_killed(); No reason to supply THD as this is part of the given structure.
set_thd_in_use_temporary_tables() removed as in_use is set on usage in sql_base.cc
sql_thd -> sql_driver_thd
More DBUG
Added update_state_of_relay_log() which will calculate the IN_STMT and IN_TRANSACTION state of the relay log after the current element is executed.
If slave_skip_counter is set run things in single threaded mode.
Simplifed arguments to io_salve_killed(), check_io_slave_killed() and sql_slave_killed(); No reason to supply THD as this is part of the given structure.
Added information to thd_proc_info() which thread is waiting for slave mutex to exit.
Disabled not used function rpl_connect_master()
Updated argument to next_event()
sql/sql_base.cc:
Added mutex around usage of slave's temporary tables. The active list is always kept up to date in sql->rgi_slave->save_temporary_tables.
Clear thd->temporary_tables after query (safety)
More DBUG
When using temporary table, set table->in_use to current thd as the THD may be different for slave threads.
Some code is ifdef:ed with REMOVE_AFTER_MERGE_WITH_10 as the given code in 10.0 is not yet in this tree.
In open_table() reuse code from find_temporary_table()
sql/sql_binlog.cc:
rli->sql_thd -> rli->sql_driver_thd
Remove duplicate setting of rgi->rli
sql/sql_class.cc:
Added helper functions rgi_lock_temporary_tables() and rgi_unlock_temporary_tables()
Would have been nicer to have these inline, but there was no easy way to do that
sql/sql_class.h:
Added functions to protect slaves temporary tables
sql/sql_parse.cc:
Added DBUG_PRINT
sql/transaction.cc:
Added comment
2013-10-13 23:24:05 +02:00
|
|
|
mysql_mutex_destroy(&sleep_lock);
|
|
|
|
mysql_cond_destroy(&sleep_cond);
|
2013-07-12 14:52:05 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
|
2013-07-03 13:46:33 +02:00
|
|
|
int
|
|
|
|
event_group_new_gtid(rpl_group_info *rgi, Gtid_log_event *gev)
|
|
|
|
{
|
2015-11-29 16:51:23 +01:00
|
|
|
uint64 sub_id= rpl_global_gtid_slave_state->next_sub_id(gev->domain_id);
|
2013-07-03 13:46:33 +02:00
|
|
|
if (!sub_id)
|
|
|
|
{
|
2013-09-13 15:09:57 +02:00
|
|
|
/* Out of memory caused hash insertion to fail. */
|
2013-07-03 13:46:33 +02:00
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
rgi->gtid_sub_id= sub_id;
|
|
|
|
rgi->current_gtid.domain_id= gev->domain_id;
|
2014-06-25 15:24:11 +02:00
|
|
|
rgi->current_gtid.server_id= gev->server_id;
|
2013-07-03 13:46:33 +02:00
|
|
|
rgi->current_gtid.seq_no= gev->seq_no;
|
2014-07-08 12:54:47 +02:00
|
|
|
rgi->commit_id= gev->commit_id;
|
MDEV-5262, MDEV-5914, MDEV-5941, MDEV-6020: Deadlocks during parallel
replication causing replication to fail.
Remove the temporary fix for MDEV-5914, which used READ COMMITTED for parallel
replication worker threads. Replace it with a better, more selective solution.
The issue is with certain edge cases of InnoDB gap locks, for example between
INSERT and ranged DELETE. It is possible for the gap lock set by the DELETE to
block the INSERT, if the DELETE runs first, while the record lock set by
INSERT does not block the DELETE, if the INSERT runs first. This can cause a
conflict between the two in parallel replication on the slave even though they
ran without conflicts on the master.
With this patch, InnoDB will ask the server layer about the two involved
transactions before blocking on a gap lock. If the server layer tells InnoDB
that the transactions are already fixed wrt. commit order, as they are in
parallel replication, InnoDB will ignore the gap lock and allow the two
transactions to proceed in parallel, avoiding the conflict.
Improve the fix for MDEV-6020. When InnoDB itself detects a deadlock, it now
asks the server layer for any preferences about which transaction to roll
back. In case of parallel replication with two transactions T1 and T2 fixed to
commit T1 before T2, the server layer will ask InnoDB to roll back T2 as the
deadlock victim, not T1. This helps in some cases to avoid excessive deadlock
rollback, as T2 will in any case need to wait for T1 to complete before it can
itself commit.
Also some misc. fixes found during development and testing:
- Remove thd_rpl_is_parallel(), it is not used or needed.
- Use KILL_CONNECTION instead of KILL_QUERY when a parallel replication
worker thread is killed to resolve a deadlock with fixed commit
ordering. There are some cases, eg. in sql/sql_parse.cc, where a KILL_QUERY
can be ignored if the query otherwise completed successfully, and this
could cause the deadlock kill to be lost, so that the deadlock was not
correctly resolved.
- Fix random test failure due to missing wait_for_binlog_checkpoint.inc.
- Make sure that deadlock or other temporary errors during parallel
replication are not printed to the the error log; there were some places
around the replication code with extra error logging. These conditions can
occur occasionally and are handled automatically without breaking
replication, so they should not pollute the error log.
- Fix handling of rgi->gtid_sub_id. We need to be able to access this also at
the end of a transaction, to be able to detect and resolve deadlocks due to
commit ordering. But this value was also used as a flag to mark whether
record_gtid() had been called, by being set to zero, losing the value. Now,
introduce a separate flag rgi->gtid_pending, so rgi->gtid_sub_id remains
valid for the entire duration of the transaction.
- Fix one place where the code to handle ignored errors called reset_killed()
unconditionally, even if no error was caught that should be ignored. This
could cause loss of a deadlock kill signal, breaking deadlock detection and
resolution.
- Fix a couple of missing mysql_reset_thd_for_next_command(). This could
cause a prior error condition to remain for the next event executed,
causing assertions about errors already being set and possibly giving
incorrect error handling for following event executions.
- Fix code that cleared thd->rgi_slave in the parallel replication worker
threads after each event execution; this caused the deadlock detection and
handling code to not be able to correctly process the associated
transactions as belonging to replication worker threads.
- Remove useless error code in slave_background_kill_request().
- Fix bug where wfc->wakeup_error was not cleared at
wait_for_commit::unregister_wait_for_prior_commit(). This could cause the
error condition to wrongly propagate to a later wait_for_prior_commit(),
causing spurious ER_PRIOR_COMMIT_FAILED errors.
- Do not put the binlog background thread into the processlist. It causes
too many result differences in mtr, but also it probably is not useful
for users to pollute the process list with a system thread that does not
really perform any user-visible tasks...
2014-06-10 10:13:15 +02:00
|
|
|
rgi->gtid_pending= true;
|
2013-07-03 13:46:33 +02:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2013-07-04 13:17:01 +02:00
|
|
|
|
|
|
|
void
|
2013-07-12 14:42:48 +02:00
|
|
|
delete_or_keep_event_post_apply(rpl_group_info *rgi,
|
2013-07-04 13:17:01 +02:00
|
|
|
Log_event_type typ, Log_event *ev)
|
|
|
|
{
|
|
|
|
/*
|
|
|
|
ToDo: This needs to work on rpl_group_info, not Relay_log_info, to be
|
|
|
|
thread-safe for parallel replication.
|
|
|
|
*/
|
|
|
|
|
|
|
|
switch (typ) {
|
|
|
|
case FORMAT_DESCRIPTION_EVENT:
|
|
|
|
/*
|
|
|
|
Format_description_log_event should not be deleted because it
|
|
|
|
will be used to read info about the relay log's format;
|
|
|
|
it will be deleted when the SQL thread does not need it,
|
|
|
|
i.e. when this thread terminates.
|
|
|
|
*/
|
|
|
|
break;
|
|
|
|
case ANNOTATE_ROWS_EVENT:
|
|
|
|
/*
|
|
|
|
Annotate_rows event should not be deleted because after it has
|
|
|
|
been applied, thd->query points to the string inside this event.
|
|
|
|
The thd->query will be used to generate new Annotate_rows event
|
|
|
|
during applying the subsequent Rows events.
|
|
|
|
*/
|
2013-07-12 14:52:05 +02:00
|
|
|
rgi->set_annotate_event((Annotate_rows_log_event*) ev);
|
2013-07-04 13:17:01 +02:00
|
|
|
break;
|
2013-12-09 12:37:45 +01:00
|
|
|
case DELETE_ROWS_EVENT_V1:
|
|
|
|
case UPDATE_ROWS_EVENT_V1:
|
|
|
|
case WRITE_ROWS_EVENT_V1:
|
2013-07-04 13:17:01 +02:00
|
|
|
case DELETE_ROWS_EVENT:
|
|
|
|
case UPDATE_ROWS_EVENT:
|
|
|
|
case WRITE_ROWS_EVENT:
|
2016-10-08 06:07:26 +02:00
|
|
|
case WRITE_ROWS_COMPRESSED_EVENT:
|
|
|
|
case DELETE_ROWS_COMPRESSED_EVENT:
|
|
|
|
case UPDATE_ROWS_COMPRESSED_EVENT:
|
|
|
|
case WRITE_ROWS_COMPRESSED_EVENT_V1:
|
|
|
|
case UPDATE_ROWS_COMPRESSED_EVENT_V1:
|
|
|
|
case DELETE_ROWS_COMPRESSED_EVENT_V1:
|
2013-07-04 13:17:01 +02:00
|
|
|
/*
|
|
|
|
After the last Rows event has been applied, the saved Annotate_rows
|
|
|
|
event (if any) is not needed anymore and can be deleted.
|
|
|
|
*/
|
|
|
|
if (((Rows_log_event*)ev)->get_flags(Rows_log_event::STMT_END_F))
|
2013-07-12 14:52:05 +02:00
|
|
|
rgi->free_annotate_event();
|
2013-07-04 13:17:01 +02:00
|
|
|
/* fall through */
|
|
|
|
default:
|
|
|
|
DBUG_PRINT("info", ("Deleting the event after it has been executed"));
|
2013-07-12 14:42:48 +02:00
|
|
|
if (!rgi->is_deferred_event(ev))
|
2013-07-04 13:17:01 +02:00
|
|
|
delete ev;
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2013-09-16 14:33:49 +02:00
|
|
|
|
|
|
|
void rpl_group_info::cleanup_context(THD *thd, bool error)
|
|
|
|
{
|
2014-05-08 14:20:18 +02:00
|
|
|
DBUG_ENTER("rpl_group_info::cleanup_context");
|
Fixes for parallel slave:
- Made slaves temporary table multi-thread slave safe by adding mutex around save_temporary_table usage.
- rli->save_temporary_tables is the active list of all used temporary tables
- This is copied to THD->temporary_tables when temporary tables are opened and updated when temporary tables are closed
- Added THD->lock_temporary_tables() and THD->unlock_temporary_tables() to simplify this.
- Relay_log_info->sql_thd renamed to Relay_log_info->sql_driver_thd to avoid wrong usage for merged code.
- Added is_part_of_group() to mark functions that are part of the next function. This replaces setting IN_STMT when events are executed.
- Added is_begin(), is_commit() and is_rollback() functions to Query_log_event to simplify code.
- If slave_skip_counter is set run things in single threaded mode. This simplifies code for skipping events.
- Updating state of relay log (IN_STMT and IN_TRANSACTION) is moved to one single function: update_state_of_relay_log()
We can't use OPTION_BEGIN to check for the state anymore as the sql_driver and sql execution threads may be different.
Clear IN_STMT and IN_TRANSACTION in init_relay_log_pos() and Relay_log_info::cleanup_context() to ensure the flags doesn't survive slave restarts
is_in_group() is now independent of state of executed transaction.
- Reset thd->transaction.all.modified_non_trans_table() if we did set it for single table row events.
This was mainly for keeping the flag as documented.
- Changed slave_open_temp_tables to uint32 to be able to use atomic operators on it.
- Relay_log_info::sleep_lock -> rpl_group_info::sleep_lock
- Relay_log_info::sleep_cond -> rpl_group_info::sleep_cond
- Changed some functions to take rpl_group_info instead of Relay_log_info to make them multi-slave safe and to simplify usage
- do_shall_skip()
- continue_group()
- sql_slave_killed()
- next_event()
- Simplifed arguments to io_salve_killed(), check_io_slave_killed() and sql_slave_killed(); No reason to supply THD as this is part of the given structure.
- set_thd_in_use_temporary_tables() removed as in_use is set on usage
- Added information to thd_proc_info() which thread is waiting for slave mutex to exit.
- In open_table() reuse code from find_temporary_table()
Other things:
- More DBUG statements
- Fixed the rpl_incident.test can be run with --debug
- More comments
- Disabled not used function rpl_connect_master()
mysql-test/suite/perfschema/r/all_instances.result:
Moved sleep_lock and sleep_cond to rpl_group_info
mysql-test/suite/rpl/r/rpl_incident.result:
Updated result
mysql-test/suite/rpl/t/rpl_incident-master.opt:
Not needed anymore
mysql-test/suite/rpl/t/rpl_incident.test:
Fixed that test can be run with --debug
sql/handler.cc:
More DBUG_PRINT
sql/log.cc:
More comments
sql/log_event.cc:
Added DBUG statements
do_shall_skip(), continue_group() now takes rpl_group_info param
Use is_begin(), is_commit() and is_rollback() functions instead of inspecting query string
We don't have set slaves temporary tables 'in_use' as this is now done when tables are opened.
Removed IN_STMT flag setting. This is now done in update_state_of_relay_log()
Use IN_TRANSACTION flag to test state of relay log.
In rows_event_stmt_cleanup() reset thd->transaction.all.modified_non_trans_table if we had set this before.
sql/log_event.h:
do_shall_skip(), continue_group() now takes rpl_group_info param
Added is_part_of_group() to mark events that are part of the next event. This replaces setting IN_STMT when events are executed.
Added is_begin(), is_commit() and is_rollback() functions to Query_log_event to simplify code.
sql/log_event_old.cc:
Removed IN_STMT flag setting. This is now done in update_state_of_relay_log()
do_shall_skip(), continue_group() now takes rpl_group_info param
sql/log_event_old.h:
Added is_part_of_group() to mark events that are part of the next event.
do_shall_skip(), continue_group() now takes rpl_group_info param
sql/mysqld.cc:
Changed slave_open_temp_tables to uint32 to be able to use atomic operators on it.
Relay_log_info::sleep_lock -> Rpl_group_info::sleep_lock
Relay_log_info::sleep_cond -> Rpl_group_info::sleep_cond
sql/mysqld.h:
Updated types and names
sql/rpl_gtid.cc:
More DBUG
sql/rpl_parallel.cc:
Updated TODO section
Set thd for event that is execution
Use new is_begin(), is_commit() and is_rollback() functions.
More comments
sql/rpl_rli.cc:
sql_thd -> sql_driver_thd
Relay_log_info::sleep_lock -> rpl_group_info::sleep_lock
Relay_log_info::sleep_cond -> rpl_group_info::sleep_cond
Clear IN_STMT and IN_TRANSACTION in init_relay_log_pos() and Relay_log_info::cleanup_context() to ensure the flags doesn't survive slave restarts.
Reset table->in_use for temporary tables as the table may have been used by another THD.
Use IN_TRANSACTION instead of OPTION_BEGIN to check state of relay log.
Removed IN_STMT flag setting. This is now done in update_state_of_relay_log()
sql/rpl_rli.h:
Changed relay log state flags to bit masks instead of bit positions (most other code we have uses bit masks)
Added IN_TRANSACTION to mark if we are in a BEGIN ... COMMIT section.
save_temporary_tables is now thread safe
Relay_log_info::sleep_lock -> rpl_group_info::sleep_lock
Relay_log_info::sleep_cond -> rpl_group_info::sleep_cond
Relay_log_info->sql_thd renamed to Relay_log_info->sql_driver_thd to avoid wrong usage for merged code
is_in_group() is now independent of state of executed transaction.
sql/slave.cc:
Simplifed arguments to io_salve_killed(), sql_slave_killed() and check_io_slave_killed(); No reason to supply THD as this is part of the given structure.
set_thd_in_use_temporary_tables() removed as in_use is set on usage in sql_base.cc
sql_thd -> sql_driver_thd
More DBUG
Added update_state_of_relay_log() which will calculate the IN_STMT and IN_TRANSACTION state of the relay log after the current element is executed.
If slave_skip_counter is set run things in single threaded mode.
Simplifed arguments to io_salve_killed(), check_io_slave_killed() and sql_slave_killed(); No reason to supply THD as this is part of the given structure.
Added information to thd_proc_info() which thread is waiting for slave mutex to exit.
Disabled not used function rpl_connect_master()
Updated argument to next_event()
sql/sql_base.cc:
Added mutex around usage of slave's temporary tables. The active list is always kept up to date in sql->rgi_slave->save_temporary_tables.
Clear thd->temporary_tables after query (safety)
More DBUG
When using temporary table, set table->in_use to current thd as the THD may be different for slave threads.
Some code is ifdef:ed with REMOVE_AFTER_MERGE_WITH_10 as the given code in 10.0 is not yet in this tree.
In open_table() reuse code from find_temporary_table()
sql/sql_binlog.cc:
rli->sql_thd -> rli->sql_driver_thd
Remove duplicate setting of rgi->rli
sql/sql_class.cc:
Added helper functions rgi_lock_temporary_tables() and rgi_unlock_temporary_tables()
Would have been nicer to have these inline, but there was no easy way to do that
sql/sql_class.h:
Added functions to protect slaves temporary tables
sql/sql_parse.cc:
Added DBUG_PRINT
sql/transaction.cc:
Added comment
2013-10-13 23:24:05 +02:00
|
|
|
DBUG_PRINT("enter", ("error: %d", (int) error));
|
|
|
|
|
2013-09-16 14:33:49 +02:00
|
|
|
DBUG_ASSERT(this->thd == thd);
|
|
|
|
/*
|
|
|
|
1) Instances of Table_map_log_event, if ::do_apply_event() was called on them,
|
|
|
|
may have opened tables, which we cannot be sure have been closed (because
|
|
|
|
maybe the Rows_log_event have not been found or will not be, because slave
|
|
|
|
SQL thread is stopping, or relay log has a missing tail etc). So we close
|
|
|
|
all thread's tables. And so the table mappings have to be cancelled.
|
|
|
|
2) Rows_log_event::do_apply_event() may even have started statements or
|
|
|
|
transactions on them, which we need to rollback in case of error.
|
|
|
|
3) If finding a Format_description_log_event after a BEGIN, we also need
|
|
|
|
to rollback before continuing with the next events.
|
|
|
|
4) so we need this "context cleanup" function.
|
|
|
|
*/
|
2018-04-04 11:16:12 +02:00
|
|
|
if (unlikely(error))
|
2013-09-16 14:33:49 +02:00
|
|
|
{
|
|
|
|
trans_rollback_stmt(thd); // if a "statement transaction"
|
2014-02-05 18:01:59 +01:00
|
|
|
/* trans_rollback() also resets OPTION_GTID_BEGIN */
|
2013-09-16 14:33:49 +02:00
|
|
|
trans_rollback(thd); // if a "real transaction"
|
2014-11-25 12:19:48 +01:00
|
|
|
/*
|
|
|
|
Now that we have rolled back the transaction, make sure we do not
|
2015-03-16 10:54:47 +01:00
|
|
|
erroneously update the GTID position.
|
2014-11-25 12:19:48 +01:00
|
|
|
*/
|
|
|
|
gtid_pending= false;
|
2013-09-16 14:33:49 +02:00
|
|
|
}
|
|
|
|
m_table_map.clear_tables();
|
|
|
|
slave_close_thread_tables(thd);
|
2016-06-10 22:19:59 +02:00
|
|
|
|
2018-04-04 11:16:12 +02:00
|
|
|
if (unlikely(error))
|
Fixes for parallel slave:
- Made slaves temporary table multi-thread slave safe by adding mutex around save_temporary_table usage.
- rli->save_temporary_tables is the active list of all used temporary tables
- This is copied to THD->temporary_tables when temporary tables are opened and updated when temporary tables are closed
- Added THD->lock_temporary_tables() and THD->unlock_temporary_tables() to simplify this.
- Relay_log_info->sql_thd renamed to Relay_log_info->sql_driver_thd to avoid wrong usage for merged code.
- Added is_part_of_group() to mark functions that are part of the next function. This replaces setting IN_STMT when events are executed.
- Added is_begin(), is_commit() and is_rollback() functions to Query_log_event to simplify code.
- If slave_skip_counter is set run things in single threaded mode. This simplifies code for skipping events.
- Updating state of relay log (IN_STMT and IN_TRANSACTION) is moved to one single function: update_state_of_relay_log()
We can't use OPTION_BEGIN to check for the state anymore as the sql_driver and sql execution threads may be different.
Clear IN_STMT and IN_TRANSACTION in init_relay_log_pos() and Relay_log_info::cleanup_context() to ensure the flags doesn't survive slave restarts
is_in_group() is now independent of state of executed transaction.
- Reset thd->transaction.all.modified_non_trans_table() if we did set it for single table row events.
This was mainly for keeping the flag as documented.
- Changed slave_open_temp_tables to uint32 to be able to use atomic operators on it.
- Relay_log_info::sleep_lock -> rpl_group_info::sleep_lock
- Relay_log_info::sleep_cond -> rpl_group_info::sleep_cond
- Changed some functions to take rpl_group_info instead of Relay_log_info to make them multi-slave safe and to simplify usage
- do_shall_skip()
- continue_group()
- sql_slave_killed()
- next_event()
- Simplifed arguments to io_salve_killed(), check_io_slave_killed() and sql_slave_killed(); No reason to supply THD as this is part of the given structure.
- set_thd_in_use_temporary_tables() removed as in_use is set on usage
- Added information to thd_proc_info() which thread is waiting for slave mutex to exit.
- In open_table() reuse code from find_temporary_table()
Other things:
- More DBUG statements
- Fixed the rpl_incident.test can be run with --debug
- More comments
- Disabled not used function rpl_connect_master()
mysql-test/suite/perfschema/r/all_instances.result:
Moved sleep_lock and sleep_cond to rpl_group_info
mysql-test/suite/rpl/r/rpl_incident.result:
Updated result
mysql-test/suite/rpl/t/rpl_incident-master.opt:
Not needed anymore
mysql-test/suite/rpl/t/rpl_incident.test:
Fixed that test can be run with --debug
sql/handler.cc:
More DBUG_PRINT
sql/log.cc:
More comments
sql/log_event.cc:
Added DBUG statements
do_shall_skip(), continue_group() now takes rpl_group_info param
Use is_begin(), is_commit() and is_rollback() functions instead of inspecting query string
We don't have set slaves temporary tables 'in_use' as this is now done when tables are opened.
Removed IN_STMT flag setting. This is now done in update_state_of_relay_log()
Use IN_TRANSACTION flag to test state of relay log.
In rows_event_stmt_cleanup() reset thd->transaction.all.modified_non_trans_table if we had set this before.
sql/log_event.h:
do_shall_skip(), continue_group() now takes rpl_group_info param
Added is_part_of_group() to mark events that are part of the next event. This replaces setting IN_STMT when events are executed.
Added is_begin(), is_commit() and is_rollback() functions to Query_log_event to simplify code.
sql/log_event_old.cc:
Removed IN_STMT flag setting. This is now done in update_state_of_relay_log()
do_shall_skip(), continue_group() now takes rpl_group_info param
sql/log_event_old.h:
Added is_part_of_group() to mark events that are part of the next event.
do_shall_skip(), continue_group() now takes rpl_group_info param
sql/mysqld.cc:
Changed slave_open_temp_tables to uint32 to be able to use atomic operators on it.
Relay_log_info::sleep_lock -> Rpl_group_info::sleep_lock
Relay_log_info::sleep_cond -> Rpl_group_info::sleep_cond
sql/mysqld.h:
Updated types and names
sql/rpl_gtid.cc:
More DBUG
sql/rpl_parallel.cc:
Updated TODO section
Set thd for event that is execution
Use new is_begin(), is_commit() and is_rollback() functions.
More comments
sql/rpl_rli.cc:
sql_thd -> sql_driver_thd
Relay_log_info::sleep_lock -> rpl_group_info::sleep_lock
Relay_log_info::sleep_cond -> rpl_group_info::sleep_cond
Clear IN_STMT and IN_TRANSACTION in init_relay_log_pos() and Relay_log_info::cleanup_context() to ensure the flags doesn't survive slave restarts.
Reset table->in_use for temporary tables as the table may have been used by another THD.
Use IN_TRANSACTION instead of OPTION_BEGIN to check state of relay log.
Removed IN_STMT flag setting. This is now done in update_state_of_relay_log()
sql/rpl_rli.h:
Changed relay log state flags to bit masks instead of bit positions (most other code we have uses bit masks)
Added IN_TRANSACTION to mark if we are in a BEGIN ... COMMIT section.
save_temporary_tables is now thread safe
Relay_log_info::sleep_lock -> rpl_group_info::sleep_lock
Relay_log_info::sleep_cond -> rpl_group_info::sleep_cond
Relay_log_info->sql_thd renamed to Relay_log_info->sql_driver_thd to avoid wrong usage for merged code
is_in_group() is now independent of state of executed transaction.
sql/slave.cc:
Simplifed arguments to io_salve_killed(), sql_slave_killed() and check_io_slave_killed(); No reason to supply THD as this is part of the given structure.
set_thd_in_use_temporary_tables() removed as in_use is set on usage in sql_base.cc
sql_thd -> sql_driver_thd
More DBUG
Added update_state_of_relay_log() which will calculate the IN_STMT and IN_TRANSACTION state of the relay log after the current element is executed.
If slave_skip_counter is set run things in single threaded mode.
Simplifed arguments to io_salve_killed(), check_io_slave_killed() and sql_slave_killed(); No reason to supply THD as this is part of the given structure.
Added information to thd_proc_info() which thread is waiting for slave mutex to exit.
Disabled not used function rpl_connect_master()
Updated argument to next_event()
sql/sql_base.cc:
Added mutex around usage of slave's temporary tables. The active list is always kept up to date in sql->rgi_slave->save_temporary_tables.
Clear thd->temporary_tables after query (safety)
More DBUG
When using temporary table, set table->in_use to current thd as the THD may be different for slave threads.
Some code is ifdef:ed with REMOVE_AFTER_MERGE_WITH_10 as the given code in 10.0 is not yet in this tree.
In open_table() reuse code from find_temporary_table()
sql/sql_binlog.cc:
rli->sql_thd -> rli->sql_driver_thd
Remove duplicate setting of rgi->rli
sql/sql_class.cc:
Added helper functions rgi_lock_temporary_tables() and rgi_unlock_temporary_tables()
Would have been nicer to have these inline, but there was no easy way to do that
sql/sql_class.h:
Added functions to protect slaves temporary tables
sql/sql_parse.cc:
Added DBUG_PRINT
sql/transaction.cc:
Added comment
2013-10-13 23:24:05 +02:00
|
|
|
{
|
2013-09-16 14:33:49 +02:00
|
|
|
thd->mdl_context.release_transactional_locks();
|
Fixes for parallel slave:
- Made slaves temporary table multi-thread slave safe by adding mutex around save_temporary_table usage.
- rli->save_temporary_tables is the active list of all used temporary tables
- This is copied to THD->temporary_tables when temporary tables are opened and updated when temporary tables are closed
- Added THD->lock_temporary_tables() and THD->unlock_temporary_tables() to simplify this.
- Relay_log_info->sql_thd renamed to Relay_log_info->sql_driver_thd to avoid wrong usage for merged code.
- Added is_part_of_group() to mark functions that are part of the next function. This replaces setting IN_STMT when events are executed.
- Added is_begin(), is_commit() and is_rollback() functions to Query_log_event to simplify code.
- If slave_skip_counter is set run things in single threaded mode. This simplifies code for skipping events.
- Updating state of relay log (IN_STMT and IN_TRANSACTION) is moved to one single function: update_state_of_relay_log()
We can't use OPTION_BEGIN to check for the state anymore as the sql_driver and sql execution threads may be different.
Clear IN_STMT and IN_TRANSACTION in init_relay_log_pos() and Relay_log_info::cleanup_context() to ensure the flags doesn't survive slave restarts
is_in_group() is now independent of state of executed transaction.
- Reset thd->transaction.all.modified_non_trans_table() if we did set it for single table row events.
This was mainly for keeping the flag as documented.
- Changed slave_open_temp_tables to uint32 to be able to use atomic operators on it.
- Relay_log_info::sleep_lock -> rpl_group_info::sleep_lock
- Relay_log_info::sleep_cond -> rpl_group_info::sleep_cond
- Changed some functions to take rpl_group_info instead of Relay_log_info to make them multi-slave safe and to simplify usage
- do_shall_skip()
- continue_group()
- sql_slave_killed()
- next_event()
- Simplifed arguments to io_salve_killed(), check_io_slave_killed() and sql_slave_killed(); No reason to supply THD as this is part of the given structure.
- set_thd_in_use_temporary_tables() removed as in_use is set on usage
- Added information to thd_proc_info() which thread is waiting for slave mutex to exit.
- In open_table() reuse code from find_temporary_table()
Other things:
- More DBUG statements
- Fixed the rpl_incident.test can be run with --debug
- More comments
- Disabled not used function rpl_connect_master()
mysql-test/suite/perfschema/r/all_instances.result:
Moved sleep_lock and sleep_cond to rpl_group_info
mysql-test/suite/rpl/r/rpl_incident.result:
Updated result
mysql-test/suite/rpl/t/rpl_incident-master.opt:
Not needed anymore
mysql-test/suite/rpl/t/rpl_incident.test:
Fixed that test can be run with --debug
sql/handler.cc:
More DBUG_PRINT
sql/log.cc:
More comments
sql/log_event.cc:
Added DBUG statements
do_shall_skip(), continue_group() now takes rpl_group_info param
Use is_begin(), is_commit() and is_rollback() functions instead of inspecting query string
We don't have set slaves temporary tables 'in_use' as this is now done when tables are opened.
Removed IN_STMT flag setting. This is now done in update_state_of_relay_log()
Use IN_TRANSACTION flag to test state of relay log.
In rows_event_stmt_cleanup() reset thd->transaction.all.modified_non_trans_table if we had set this before.
sql/log_event.h:
do_shall_skip(), continue_group() now takes rpl_group_info param
Added is_part_of_group() to mark events that are part of the next event. This replaces setting IN_STMT when events are executed.
Added is_begin(), is_commit() and is_rollback() functions to Query_log_event to simplify code.
sql/log_event_old.cc:
Removed IN_STMT flag setting. This is now done in update_state_of_relay_log()
do_shall_skip(), continue_group() now takes rpl_group_info param
sql/log_event_old.h:
Added is_part_of_group() to mark events that are part of the next event.
do_shall_skip(), continue_group() now takes rpl_group_info param
sql/mysqld.cc:
Changed slave_open_temp_tables to uint32 to be able to use atomic operators on it.
Relay_log_info::sleep_lock -> Rpl_group_info::sleep_lock
Relay_log_info::sleep_cond -> Rpl_group_info::sleep_cond
sql/mysqld.h:
Updated types and names
sql/rpl_gtid.cc:
More DBUG
sql/rpl_parallel.cc:
Updated TODO section
Set thd for event that is execution
Use new is_begin(), is_commit() and is_rollback() functions.
More comments
sql/rpl_rli.cc:
sql_thd -> sql_driver_thd
Relay_log_info::sleep_lock -> rpl_group_info::sleep_lock
Relay_log_info::sleep_cond -> rpl_group_info::sleep_cond
Clear IN_STMT and IN_TRANSACTION in init_relay_log_pos() and Relay_log_info::cleanup_context() to ensure the flags doesn't survive slave restarts.
Reset table->in_use for temporary tables as the table may have been used by another THD.
Use IN_TRANSACTION instead of OPTION_BEGIN to check state of relay log.
Removed IN_STMT flag setting. This is now done in update_state_of_relay_log()
sql/rpl_rli.h:
Changed relay log state flags to bit masks instead of bit positions (most other code we have uses bit masks)
Added IN_TRANSACTION to mark if we are in a BEGIN ... COMMIT section.
save_temporary_tables is now thread safe
Relay_log_info::sleep_lock -> rpl_group_info::sleep_lock
Relay_log_info::sleep_cond -> rpl_group_info::sleep_cond
Relay_log_info->sql_thd renamed to Relay_log_info->sql_driver_thd to avoid wrong usage for merged code
is_in_group() is now independent of state of executed transaction.
sql/slave.cc:
Simplifed arguments to io_salve_killed(), sql_slave_killed() and check_io_slave_killed(); No reason to supply THD as this is part of the given structure.
set_thd_in_use_temporary_tables() removed as in_use is set on usage in sql_base.cc
sql_thd -> sql_driver_thd
More DBUG
Added update_state_of_relay_log() which will calculate the IN_STMT and IN_TRANSACTION state of the relay log after the current element is executed.
If slave_skip_counter is set run things in single threaded mode.
Simplifed arguments to io_salve_killed(), check_io_slave_killed() and sql_slave_killed(); No reason to supply THD as this is part of the given structure.
Added information to thd_proc_info() which thread is waiting for slave mutex to exit.
Disabled not used function rpl_connect_master()
Updated argument to next_event()
sql/sql_base.cc:
Added mutex around usage of slave's temporary tables. The active list is always kept up to date in sql->rgi_slave->save_temporary_tables.
Clear thd->temporary_tables after query (safety)
More DBUG
When using temporary table, set table->in_use to current thd as the THD may be different for slave threads.
Some code is ifdef:ed with REMOVE_AFTER_MERGE_WITH_10 as the given code in 10.0 is not yet in this tree.
In open_table() reuse code from find_temporary_table()
sql/sql_binlog.cc:
rli->sql_thd -> rli->sql_driver_thd
Remove duplicate setting of rgi->rli
sql/sql_class.cc:
Added helper functions rgi_lock_temporary_tables() and rgi_unlock_temporary_tables()
Would have been nicer to have these inline, but there was no easy way to do that
sql/sql_class.h:
Added functions to protect slaves temporary tables
sql/sql_parse.cc:
Added DBUG_PRINT
sql/transaction.cc:
Added comment
2013-10-13 23:24:05 +02:00
|
|
|
|
|
|
|
if (thd == rli->sql_driver_thd)
|
|
|
|
{
|
|
|
|
/*
|
|
|
|
Reset flags. This is needed to handle incident events and errors in
|
|
|
|
the relay log noticed by the sql driver thread.
|
|
|
|
*/
|
|
|
|
rli->clear_flag(Relay_log_info::IN_STMT);
|
|
|
|
rli->clear_flag(Relay_log_info::IN_TRANSACTION);
|
|
|
|
}
|
2015-06-23 14:10:14 +02:00
|
|
|
|
|
|
|
/*
|
|
|
|
Ensure we always release the domain for others to process, when using
|
|
|
|
--gtid-ignore-duplicates.
|
|
|
|
*/
|
|
|
|
if (gtid_ignore_duplicate_state != GTID_DUPLICATE_NULL)
|
2015-11-29 16:51:23 +01:00
|
|
|
rpl_global_gtid_slave_state->release_domain_owner(this);
|
Fixes for parallel slave:
- Made slaves temporary table multi-thread slave safe by adding mutex around save_temporary_table usage.
- rli->save_temporary_tables is the active list of all used temporary tables
- This is copied to THD->temporary_tables when temporary tables are opened and updated when temporary tables are closed
- Added THD->lock_temporary_tables() and THD->unlock_temporary_tables() to simplify this.
- Relay_log_info->sql_thd renamed to Relay_log_info->sql_driver_thd to avoid wrong usage for merged code.
- Added is_part_of_group() to mark functions that are part of the next function. This replaces setting IN_STMT when events are executed.
- Added is_begin(), is_commit() and is_rollback() functions to Query_log_event to simplify code.
- If slave_skip_counter is set run things in single threaded mode. This simplifies code for skipping events.
- Updating state of relay log (IN_STMT and IN_TRANSACTION) is moved to one single function: update_state_of_relay_log()
We can't use OPTION_BEGIN to check for the state anymore as the sql_driver and sql execution threads may be different.
Clear IN_STMT and IN_TRANSACTION in init_relay_log_pos() and Relay_log_info::cleanup_context() to ensure the flags doesn't survive slave restarts
is_in_group() is now independent of state of executed transaction.
- Reset thd->transaction.all.modified_non_trans_table() if we did set it for single table row events.
This was mainly for keeping the flag as documented.
- Changed slave_open_temp_tables to uint32 to be able to use atomic operators on it.
- Relay_log_info::sleep_lock -> rpl_group_info::sleep_lock
- Relay_log_info::sleep_cond -> rpl_group_info::sleep_cond
- Changed some functions to take rpl_group_info instead of Relay_log_info to make them multi-slave safe and to simplify usage
- do_shall_skip()
- continue_group()
- sql_slave_killed()
- next_event()
- Simplifed arguments to io_salve_killed(), check_io_slave_killed() and sql_slave_killed(); No reason to supply THD as this is part of the given structure.
- set_thd_in_use_temporary_tables() removed as in_use is set on usage
- Added information to thd_proc_info() which thread is waiting for slave mutex to exit.
- In open_table() reuse code from find_temporary_table()
Other things:
- More DBUG statements
- Fixed the rpl_incident.test can be run with --debug
- More comments
- Disabled not used function rpl_connect_master()
mysql-test/suite/perfschema/r/all_instances.result:
Moved sleep_lock and sleep_cond to rpl_group_info
mysql-test/suite/rpl/r/rpl_incident.result:
Updated result
mysql-test/suite/rpl/t/rpl_incident-master.opt:
Not needed anymore
mysql-test/suite/rpl/t/rpl_incident.test:
Fixed that test can be run with --debug
sql/handler.cc:
More DBUG_PRINT
sql/log.cc:
More comments
sql/log_event.cc:
Added DBUG statements
do_shall_skip(), continue_group() now takes rpl_group_info param
Use is_begin(), is_commit() and is_rollback() functions instead of inspecting query string
We don't have set slaves temporary tables 'in_use' as this is now done when tables are opened.
Removed IN_STMT flag setting. This is now done in update_state_of_relay_log()
Use IN_TRANSACTION flag to test state of relay log.
In rows_event_stmt_cleanup() reset thd->transaction.all.modified_non_trans_table if we had set this before.
sql/log_event.h:
do_shall_skip(), continue_group() now takes rpl_group_info param
Added is_part_of_group() to mark events that are part of the next event. This replaces setting IN_STMT when events are executed.
Added is_begin(), is_commit() and is_rollback() functions to Query_log_event to simplify code.
sql/log_event_old.cc:
Removed IN_STMT flag setting. This is now done in update_state_of_relay_log()
do_shall_skip(), continue_group() now takes rpl_group_info param
sql/log_event_old.h:
Added is_part_of_group() to mark events that are part of the next event.
do_shall_skip(), continue_group() now takes rpl_group_info param
sql/mysqld.cc:
Changed slave_open_temp_tables to uint32 to be able to use atomic operators on it.
Relay_log_info::sleep_lock -> Rpl_group_info::sleep_lock
Relay_log_info::sleep_cond -> Rpl_group_info::sleep_cond
sql/mysqld.h:
Updated types and names
sql/rpl_gtid.cc:
More DBUG
sql/rpl_parallel.cc:
Updated TODO section
Set thd for event that is execution
Use new is_begin(), is_commit() and is_rollback() functions.
More comments
sql/rpl_rli.cc:
sql_thd -> sql_driver_thd
Relay_log_info::sleep_lock -> rpl_group_info::sleep_lock
Relay_log_info::sleep_cond -> rpl_group_info::sleep_cond
Clear IN_STMT and IN_TRANSACTION in init_relay_log_pos() and Relay_log_info::cleanup_context() to ensure the flags doesn't survive slave restarts.
Reset table->in_use for temporary tables as the table may have been used by another THD.
Use IN_TRANSACTION instead of OPTION_BEGIN to check state of relay log.
Removed IN_STMT flag setting. This is now done in update_state_of_relay_log()
sql/rpl_rli.h:
Changed relay log state flags to bit masks instead of bit positions (most other code we have uses bit masks)
Added IN_TRANSACTION to mark if we are in a BEGIN ... COMMIT section.
save_temporary_tables is now thread safe
Relay_log_info::sleep_lock -> rpl_group_info::sleep_lock
Relay_log_info::sleep_cond -> rpl_group_info::sleep_cond
Relay_log_info->sql_thd renamed to Relay_log_info->sql_driver_thd to avoid wrong usage for merged code
is_in_group() is now independent of state of executed transaction.
sql/slave.cc:
Simplifed arguments to io_salve_killed(), sql_slave_killed() and check_io_slave_killed(); No reason to supply THD as this is part of the given structure.
set_thd_in_use_temporary_tables() removed as in_use is set on usage in sql_base.cc
sql_thd -> sql_driver_thd
More DBUG
Added update_state_of_relay_log() which will calculate the IN_STMT and IN_TRANSACTION state of the relay log after the current element is executed.
If slave_skip_counter is set run things in single threaded mode.
Simplifed arguments to io_salve_killed(), check_io_slave_killed() and sql_slave_killed(); No reason to supply THD as this is part of the given structure.
Added information to thd_proc_info() which thread is waiting for slave mutex to exit.
Disabled not used function rpl_connect_master()
Updated argument to next_event()
sql/sql_base.cc:
Added mutex around usage of slave's temporary tables. The active list is always kept up to date in sql->rgi_slave->save_temporary_tables.
Clear thd->temporary_tables after query (safety)
More DBUG
When using temporary table, set table->in_use to current thd as the THD may be different for slave threads.
Some code is ifdef:ed with REMOVE_AFTER_MERGE_WITH_10 as the given code in 10.0 is not yet in this tree.
In open_table() reuse code from find_temporary_table()
sql/sql_binlog.cc:
rli->sql_thd -> rli->sql_driver_thd
Remove duplicate setting of rgi->rli
sql/sql_class.cc:
Added helper functions rgi_lock_temporary_tables() and rgi_unlock_temporary_tables()
Would have been nicer to have these inline, but there was no easy way to do that
sql/sql_class.h:
Added functions to protect slaves temporary tables
sql/sql_parse.cc:
Added DBUG_PRINT
sql/transaction.cc:
Added comment
2013-10-13 23:24:05 +02:00
|
|
|
}
|
|
|
|
|
2013-09-16 14:33:49 +02:00
|
|
|
/*
|
|
|
|
Cleanup for the flags that have been set at do_apply_event.
|
|
|
|
*/
|
2016-06-29 09:14:22 +02:00
|
|
|
thd->variables.option_bits&= ~(OPTION_NO_FOREIGN_KEY_CHECKS |
|
|
|
|
OPTION_RELAXED_UNIQUE_CHECKS |
|
|
|
|
OPTION_NO_CHECK_CONSTRAINT_CHECKS);
|
2013-09-16 14:33:49 +02:00
|
|
|
|
|
|
|
/*
|
|
|
|
Reset state related to long_find_row notes in the error log:
|
|
|
|
- timestamp
|
|
|
|
- flag that decides whether the slave prints or not
|
|
|
|
*/
|
2013-10-14 23:17:16 +02:00
|
|
|
reset_row_stmt_start_timestamp();
|
|
|
|
unset_long_find_row_note_printed();
|
2013-09-16 14:33:49 +02:00
|
|
|
|
2015-06-23 14:10:14 +02:00
|
|
|
DBUG_EXECUTE_IF("inject_sleep_gtid_100_x_x", {
|
|
|
|
if (current_gtid.domain_id == 100)
|
|
|
|
my_sleep(50000);
|
|
|
|
};);
|
|
|
|
|
2013-09-16 14:33:49 +02:00
|
|
|
DBUG_VOID_RETURN;
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
void rpl_group_info::clear_tables_to_lock()
|
|
|
|
{
|
2014-05-08 14:20:18 +02:00
|
|
|
DBUG_ENTER("rpl_group_info::clear_tables_to_lock()");
|
2013-09-16 14:33:49 +02:00
|
|
|
#ifndef DBUG_OFF
|
|
|
|
/**
|
|
|
|
When replicating in RBR and MyISAM Merge tables are involved
|
|
|
|
open_and_lock_tables (called in do_apply_event) appends the
|
|
|
|
base tables to the list of tables_to_lock. Then these are
|
|
|
|
removed from the list in close_thread_tables (which is called
|
|
|
|
before we reach this point).
|
|
|
|
|
|
|
|
This assertion just confirms that we get no surprises at this
|
|
|
|
point.
|
|
|
|
*/
|
|
|
|
uint i=0;
|
|
|
|
for (TABLE_LIST *ptr= tables_to_lock ; ptr ; ptr= ptr->next_global, i++) ;
|
|
|
|
DBUG_ASSERT(i == tables_to_lock_count);
|
|
|
|
#endif
|
|
|
|
|
|
|
|
while (tables_to_lock)
|
|
|
|
{
|
|
|
|
uchar* to_free= reinterpret_cast<uchar*>(tables_to_lock);
|
|
|
|
if (tables_to_lock->m_tabledef_valid)
|
|
|
|
{
|
|
|
|
tables_to_lock->m_tabledef.table_def::~table_def();
|
|
|
|
tables_to_lock->m_tabledef_valid= FALSE;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
If blob fields were used during conversion of field values
|
|
|
|
from the master table into the slave table, then we need to
|
|
|
|
free the memory used temporarily to store their values before
|
|
|
|
copying into the slave's table.
|
|
|
|
*/
|
|
|
|
if (tables_to_lock->m_conv_table)
|
|
|
|
free_blobs(tables_to_lock->m_conv_table);
|
|
|
|
|
|
|
|
tables_to_lock=
|
|
|
|
static_cast<RPL_TABLE_LIST*>(tables_to_lock->next_global);
|
|
|
|
tables_to_lock_count--;
|
|
|
|
my_free(to_free);
|
|
|
|
}
|
|
|
|
DBUG_ASSERT(tables_to_lock == NULL && tables_to_lock_count == 0);
|
|
|
|
DBUG_VOID_RETURN;
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
void rpl_group_info::slave_close_thread_tables(THD *thd)
|
|
|
|
{
|
2014-05-08 14:20:18 +02:00
|
|
|
DBUG_ENTER("rpl_group_info::slave_close_thread_tables(THD *thd)");
|
2013-11-01 12:00:11 +01:00
|
|
|
thd->get_stmt_da()->set_overwrite_status(true);
|
2013-09-16 14:33:49 +02:00
|
|
|
thd->is_error() ? trans_rollback_stmt(thd) : trans_commit_stmt(thd);
|
2013-11-01 12:00:11 +01:00
|
|
|
thd->get_stmt_da()->set_overwrite_status(false);
|
2013-09-16 14:33:49 +02:00
|
|
|
|
|
|
|
close_thread_tables(thd);
|
|
|
|
/*
|
2013-08-20 11:12:34 +02:00
|
|
|
- If transaction rollback was requested due to deadlock
|
|
|
|
perform it and release metadata locks.
|
2013-09-16 14:33:49 +02:00
|
|
|
- If inside a multi-statement transaction,
|
|
|
|
defer the release of metadata locks until the current
|
|
|
|
transaction is either committed or rolled back. This prevents
|
|
|
|
other statements from modifying the table for the entire
|
|
|
|
duration of this transaction. This provides commit ordering
|
|
|
|
and guarantees serializability across multiple transactions.
|
|
|
|
- If in autocommit mode, or outside a transactional context,
|
|
|
|
automatically release metadata locks of the current statement.
|
|
|
|
*/
|
2013-08-20 11:12:34 +02:00
|
|
|
if (thd->transaction_rollback_request)
|
|
|
|
{
|
|
|
|
trans_rollback_implicit(thd);
|
|
|
|
thd->mdl_context.release_transactional_locks();
|
|
|
|
}
|
|
|
|
else if (! thd->in_multi_stmt_transaction_mode())
|
2013-09-16 14:33:49 +02:00
|
|
|
thd->mdl_context.release_transactional_locks();
|
|
|
|
else
|
|
|
|
thd->mdl_context.release_statement_locks();
|
|
|
|
|
|
|
|
clear_tables_to_lock();
|
|
|
|
DBUG_VOID_RETURN;
|
|
|
|
}
|
|
|
|
|
|
|
|
|
MDEV-5657: Parallel replication.
Clean up and improve the parallel implementation code, mainly related to
scheduling of work to threads and handling of stop and errors.
Fix a lot of bugs in various corner cases that could lead to crashes or
corruption.
Fix that a single replication domain could easily grab all worker threads and
stall all other domains; now a configuration variable
--slave-domain-parallel-threads allows to limit the number of
workers.
Allow next event group to start as soon as previous group begins the commit
phase (as opposed to when it ends it); this allows multiple event groups on
the slave to participate in group commit, even when no other opportunities for
parallelism are available.
Various fixes:
- Fix some races in the rpl.rpl_parallel test case.
- Fix an old incorrect assertion in Log_event iocache read.
- Fix repeated malloc/free of wait_for_commit and rpl_group_info objects.
- Simplify wait_for_commit wakeup logic.
- Fix one case in queue_for_group_commit() where killing one thread would
fail to correctly signal the error to the next, causing loss of the
transaction after slave restart.
- Fix leaking of pthreads (and their allocated stack) due to missing
PTHREAD_CREATE_DETACHED attribute.
- Fix how one batch of group-committed transactions wait for the previous
batch before starting to execute themselves. The old code had a very
complex scheduling where the first transaction was handled differently,
with subtle bugs in corner cases. Now each event group is always scheduled
for a new worker (in a round-robin fashion amongst available workers).
Keep a count of how many transactions have started to commit, and wait for
that counter to reach the appropriate value.
- Fix slave stop to wait for all workers to actually complete processing;
before, the wait was for update of last_committed_sub_id, which happens a
bit earlier, and could leave worker threads potentially accessing bits of
the replication state that is no longer valid after slave stop.
- Fix a couple of places where the test suite would kill a thread waiting
inside enter_cond() in connection with debug_sync; debug_sync + kill can
crash in rare cases due to a race with mysys_var_current_mutex in this
case.
- Fix some corner cases where we had enter_cond() but no exit_cond().
- Fix that we could get failure in wait_for_prior_commit() but forget to flag
the error with my_error().
- Fix slave stop (both for normal stop and stop due to error). Now, at stop
we pick a specific safe point (in terms of event groups executed) and make
sure that all event groups before that point are executed to completion,
and that no event group after start executing; this ensures a safe place to
restart replication, even for non-transactional stuff/DDL. In error stop,
make sure that all prior event groups are allowed to execute to completion,
and that any later event groups that have started are rolled back, if
possible. The old code could leave eg. T1 and T3 committed but T2 not, or
it could even leave half a transaction not rolled back in some random
worker, which would cause big problems when that worker was later reused
after slave restart.
- Fix the accounting of amount of events queued for one worker. Before, the
amount was reduced immediately as soon as the events were dequeued (which
happens all at once); this allowed twice the amount of events to be queued
in memory for each single worker, which is not what users would expect.
- Fix that an error set during execution of one event was sometimes not
cleared before executing the next, causing problems with the error
reporting.
- Fix incorrect handling of thd->killed in worker threads.
2014-02-26 15:02:09 +01:00
|
|
|
|
|
|
|
static void
|
2015-01-07 14:45:39 +01:00
|
|
|
mark_start_commit_inner(rpl_parallel_entry *e, group_commit_orderer *gco,
|
|
|
|
rpl_group_info *rgi)
|
MDEV-5657: Parallel replication.
Clean up and improve the parallel implementation code, mainly related to
scheduling of work to threads and handling of stop and errors.
Fix a lot of bugs in various corner cases that could lead to crashes or
corruption.
Fix that a single replication domain could easily grab all worker threads and
stall all other domains; now a configuration variable
--slave-domain-parallel-threads allows to limit the number of
workers.
Allow next event group to start as soon as previous group begins the commit
phase (as opposed to when it ends it); this allows multiple event groups on
the slave to participate in group commit, even when no other opportunities for
parallelism are available.
Various fixes:
- Fix some races in the rpl.rpl_parallel test case.
- Fix an old incorrect assertion in Log_event iocache read.
- Fix repeated malloc/free of wait_for_commit and rpl_group_info objects.
- Simplify wait_for_commit wakeup logic.
- Fix one case in queue_for_group_commit() where killing one thread would
fail to correctly signal the error to the next, causing loss of the
transaction after slave restart.
- Fix leaking of pthreads (and their allocated stack) due to missing
PTHREAD_CREATE_DETACHED attribute.
- Fix how one batch of group-committed transactions wait for the previous
batch before starting to execute themselves. The old code had a very
complex scheduling where the first transaction was handled differently,
with subtle bugs in corner cases. Now each event group is always scheduled
for a new worker (in a round-robin fashion amongst available workers).
Keep a count of how many transactions have started to commit, and wait for
that counter to reach the appropriate value.
- Fix slave stop to wait for all workers to actually complete processing;
before, the wait was for update of last_committed_sub_id, which happens a
bit earlier, and could leave worker threads potentially accessing bits of
the replication state that is no longer valid after slave stop.
- Fix a couple of places where the test suite would kill a thread waiting
inside enter_cond() in connection with debug_sync; debug_sync + kill can
crash in rare cases due to a race with mysys_var_current_mutex in this
case.
- Fix some corner cases where we had enter_cond() but no exit_cond().
- Fix that we could get failure in wait_for_prior_commit() but forget to flag
the error with my_error().
- Fix slave stop (both for normal stop and stop due to error). Now, at stop
we pick a specific safe point (in terms of event groups executed) and make
sure that all event groups before that point are executed to completion,
and that no event group after start executing; this ensures a safe place to
restart replication, even for non-transactional stuff/DDL. In error stop,
make sure that all prior event groups are allowed to execute to completion,
and that any later event groups that have started are rolled back, if
possible. The old code could leave eg. T1 and T3 committed but T2 not, or
it could even leave half a transaction not rolled back in some random
worker, which would cause big problems when that worker was later reused
after slave restart.
- Fix the accounting of amount of events queued for one worker. Before, the
amount was reduced immediately as soon as the events were dequeued (which
happens all at once); this allowed twice the amount of events to be queued
in memory for each single worker, which is not what users would expect.
- Fix that an error set during execution of one event was sometimes not
cleared before executing the next, causing problems with the error
reporting.
- Fix incorrect handling of thd->killed in worker threads.
2014-02-26 15:02:09 +01:00
|
|
|
{
|
2015-01-07 14:45:39 +01:00
|
|
|
group_commit_orderer *tmp;
|
MDEV-5657: Parallel replication.
Clean up and improve the parallel implementation code, mainly related to
scheduling of work to threads and handling of stop and errors.
Fix a lot of bugs in various corner cases that could lead to crashes or
corruption.
Fix that a single replication domain could easily grab all worker threads and
stall all other domains; now a configuration variable
--slave-domain-parallel-threads allows to limit the number of
workers.
Allow next event group to start as soon as previous group begins the commit
phase (as opposed to when it ends it); this allows multiple event groups on
the slave to participate in group commit, even when no other opportunities for
parallelism are available.
Various fixes:
- Fix some races in the rpl.rpl_parallel test case.
- Fix an old incorrect assertion in Log_event iocache read.
- Fix repeated malloc/free of wait_for_commit and rpl_group_info objects.
- Simplify wait_for_commit wakeup logic.
- Fix one case in queue_for_group_commit() where killing one thread would
fail to correctly signal the error to the next, causing loss of the
transaction after slave restart.
- Fix leaking of pthreads (and their allocated stack) due to missing
PTHREAD_CREATE_DETACHED attribute.
- Fix how one batch of group-committed transactions wait for the previous
batch before starting to execute themselves. The old code had a very
complex scheduling where the first transaction was handled differently,
with subtle bugs in corner cases. Now each event group is always scheduled
for a new worker (in a round-robin fashion amongst available workers).
Keep a count of how many transactions have started to commit, and wait for
that counter to reach the appropriate value.
- Fix slave stop to wait for all workers to actually complete processing;
before, the wait was for update of last_committed_sub_id, which happens a
bit earlier, and could leave worker threads potentially accessing bits of
the replication state that is no longer valid after slave stop.
- Fix a couple of places where the test suite would kill a thread waiting
inside enter_cond() in connection with debug_sync; debug_sync + kill can
crash in rare cases due to a race with mysys_var_current_mutex in this
case.
- Fix some corner cases where we had enter_cond() but no exit_cond().
- Fix that we could get failure in wait_for_prior_commit() but forget to flag
the error with my_error().
- Fix slave stop (both for normal stop and stop due to error). Now, at stop
we pick a specific safe point (in terms of event groups executed) and make
sure that all event groups before that point are executed to completion,
and that no event group after start executing; this ensures a safe place to
restart replication, even for non-transactional stuff/DDL. In error stop,
make sure that all prior event groups are allowed to execute to completion,
and that any later event groups that have started are rolled back, if
possible. The old code could leave eg. T1 and T3 committed but T2 not, or
it could even leave half a transaction not rolled back in some random
worker, which would cause big problems when that worker was later reused
after slave restart.
- Fix the accounting of amount of events queued for one worker. Before, the
amount was reduced immediately as soon as the events were dequeued (which
happens all at once); this allowed twice the amount of events to be queued
in memory for each single worker, which is not what users would expect.
- Fix that an error set during execution of one event was sometimes not
cleared before executing the next, causing problems with the error
reporting.
- Fix incorrect handling of thd->killed in worker threads.
2014-02-26 15:02:09 +01:00
|
|
|
uint64 count= ++e->count_committing_event_groups;
|
2015-01-07 14:45:39 +01:00
|
|
|
/* Signal any following GCO whose wait_count has been reached now. */
|
|
|
|
tmp= gco;
|
|
|
|
while ((tmp= tmp->next_gco))
|
|
|
|
{
|
|
|
|
uint64 wait_count= tmp->wait_count;
|
|
|
|
if (wait_count > count)
|
|
|
|
break;
|
|
|
|
mysql_cond_broadcast(&tmp->COND_group_commit_orderer);
|
|
|
|
}
|
MDEV-5657: Parallel replication.
Clean up and improve the parallel implementation code, mainly related to
scheduling of work to threads and handling of stop and errors.
Fix a lot of bugs in various corner cases that could lead to crashes or
corruption.
Fix that a single replication domain could easily grab all worker threads and
stall all other domains; now a configuration variable
--slave-domain-parallel-threads allows to limit the number of
workers.
Allow next event group to start as soon as previous group begins the commit
phase (as opposed to when it ends it); this allows multiple event groups on
the slave to participate in group commit, even when no other opportunities for
parallelism are available.
Various fixes:
- Fix some races in the rpl.rpl_parallel test case.
- Fix an old incorrect assertion in Log_event iocache read.
- Fix repeated malloc/free of wait_for_commit and rpl_group_info objects.
- Simplify wait_for_commit wakeup logic.
- Fix one case in queue_for_group_commit() where killing one thread would
fail to correctly signal the error to the next, causing loss of the
transaction after slave restart.
- Fix leaking of pthreads (and their allocated stack) due to missing
PTHREAD_CREATE_DETACHED attribute.
- Fix how one batch of group-committed transactions wait for the previous
batch before starting to execute themselves. The old code had a very
complex scheduling where the first transaction was handled differently,
with subtle bugs in corner cases. Now each event group is always scheduled
for a new worker (in a round-robin fashion amongst available workers).
Keep a count of how many transactions have started to commit, and wait for
that counter to reach the appropriate value.
- Fix slave stop to wait for all workers to actually complete processing;
before, the wait was for update of last_committed_sub_id, which happens a
bit earlier, and could leave worker threads potentially accessing bits of
the replication state that is no longer valid after slave stop.
- Fix a couple of places where the test suite would kill a thread waiting
inside enter_cond() in connection with debug_sync; debug_sync + kill can
crash in rare cases due to a race with mysys_var_current_mutex in this
case.
- Fix some corner cases where we had enter_cond() but no exit_cond().
- Fix that we could get failure in wait_for_prior_commit() but forget to flag
the error with my_error().
- Fix slave stop (both for normal stop and stop due to error). Now, at stop
we pick a specific safe point (in terms of event groups executed) and make
sure that all event groups before that point are executed to completion,
and that no event group after start executing; this ensures a safe place to
restart replication, even for non-transactional stuff/DDL. In error stop,
make sure that all prior event groups are allowed to execute to completion,
and that any later event groups that have started are rolled back, if
possible. The old code could leave eg. T1 and T3 committed but T2 not, or
it could even leave half a transaction not rolled back in some random
worker, which would cause big problems when that worker was later reused
after slave restart.
- Fix the accounting of amount of events queued for one worker. Before, the
amount was reduced immediately as soon as the events were dequeued (which
happens all at once); this allowed twice the amount of events to be queued
in memory for each single worker, which is not what users would expect.
- Fix that an error set during execution of one event was sometimes not
cleared before executing the next, causing problems with the error
reporting.
- Fix incorrect handling of thd->killed in worker threads.
2014-02-26 15:02:09 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
void
|
|
|
|
rpl_group_info::mark_start_commit_no_lock()
|
|
|
|
{
|
|
|
|
if (did_mark_start_commit)
|
|
|
|
return;
|
|
|
|
did_mark_start_commit= true;
|
2016-08-22 09:16:00 +02:00
|
|
|
mark_start_commit_inner(parallel_entry, gco, this);
|
MDEV-5657: Parallel replication.
Clean up and improve the parallel implementation code, mainly related to
scheduling of work to threads and handling of stop and errors.
Fix a lot of bugs in various corner cases that could lead to crashes or
corruption.
Fix that a single replication domain could easily grab all worker threads and
stall all other domains; now a configuration variable
--slave-domain-parallel-threads allows to limit the number of
workers.
Allow next event group to start as soon as previous group begins the commit
phase (as opposed to when it ends it); this allows multiple event groups on
the slave to participate in group commit, even when no other opportunities for
parallelism are available.
Various fixes:
- Fix some races in the rpl.rpl_parallel test case.
- Fix an old incorrect assertion in Log_event iocache read.
- Fix repeated malloc/free of wait_for_commit and rpl_group_info objects.
- Simplify wait_for_commit wakeup logic.
- Fix one case in queue_for_group_commit() where killing one thread would
fail to correctly signal the error to the next, causing loss of the
transaction after slave restart.
- Fix leaking of pthreads (and their allocated stack) due to missing
PTHREAD_CREATE_DETACHED attribute.
- Fix how one batch of group-committed transactions wait for the previous
batch before starting to execute themselves. The old code had a very
complex scheduling where the first transaction was handled differently,
with subtle bugs in corner cases. Now each event group is always scheduled
for a new worker (in a round-robin fashion amongst available workers).
Keep a count of how many transactions have started to commit, and wait for
that counter to reach the appropriate value.
- Fix slave stop to wait for all workers to actually complete processing;
before, the wait was for update of last_committed_sub_id, which happens a
bit earlier, and could leave worker threads potentially accessing bits of
the replication state that is no longer valid after slave stop.
- Fix a couple of places where the test suite would kill a thread waiting
inside enter_cond() in connection with debug_sync; debug_sync + kill can
crash in rare cases due to a race with mysys_var_current_mutex in this
case.
- Fix some corner cases where we had enter_cond() but no exit_cond().
- Fix that we could get failure in wait_for_prior_commit() but forget to flag
the error with my_error().
- Fix slave stop (both for normal stop and stop due to error). Now, at stop
we pick a specific safe point (in terms of event groups executed) and make
sure that all event groups before that point are executed to completion,
and that no event group after start executing; this ensures a safe place to
restart replication, even for non-transactional stuff/DDL. In error stop,
make sure that all prior event groups are allowed to execute to completion,
and that any later event groups that have started are rolled back, if
possible. The old code could leave eg. T1 and T3 committed but T2 not, or
it could even leave half a transaction not rolled back in some random
worker, which would cause big problems when that worker was later reused
after slave restart.
- Fix the accounting of amount of events queued for one worker. Before, the
amount was reduced immediately as soon as the events were dequeued (which
happens all at once); this allowed twice the amount of events to be queued
in memory for each single worker, which is not what users would expect.
- Fix that an error set during execution of one event was sometimes not
cleared before executing the next, causing problems with the error
reporting.
- Fix incorrect handling of thd->killed in worker threads.
2014-02-26 15:02:09 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
void
|
|
|
|
rpl_group_info::mark_start_commit()
|
|
|
|
{
|
|
|
|
rpl_parallel_entry *e;
|
|
|
|
|
|
|
|
if (did_mark_start_commit)
|
|
|
|
return;
|
2016-08-22 09:16:00 +02:00
|
|
|
did_mark_start_commit= true;
|
MDEV-5657: Parallel replication.
Clean up and improve the parallel implementation code, mainly related to
scheduling of work to threads and handling of stop and errors.
Fix a lot of bugs in various corner cases that could lead to crashes or
corruption.
Fix that a single replication domain could easily grab all worker threads and
stall all other domains; now a configuration variable
--slave-domain-parallel-threads allows to limit the number of
workers.
Allow next event group to start as soon as previous group begins the commit
phase (as opposed to when it ends it); this allows multiple event groups on
the slave to participate in group commit, even when no other opportunities for
parallelism are available.
Various fixes:
- Fix some races in the rpl.rpl_parallel test case.
- Fix an old incorrect assertion in Log_event iocache read.
- Fix repeated malloc/free of wait_for_commit and rpl_group_info objects.
- Simplify wait_for_commit wakeup logic.
- Fix one case in queue_for_group_commit() where killing one thread would
fail to correctly signal the error to the next, causing loss of the
transaction after slave restart.
- Fix leaking of pthreads (and their allocated stack) due to missing
PTHREAD_CREATE_DETACHED attribute.
- Fix how one batch of group-committed transactions wait for the previous
batch before starting to execute themselves. The old code had a very
complex scheduling where the first transaction was handled differently,
with subtle bugs in corner cases. Now each event group is always scheduled
for a new worker (in a round-robin fashion amongst available workers).
Keep a count of how many transactions have started to commit, and wait for
that counter to reach the appropriate value.
- Fix slave stop to wait for all workers to actually complete processing;
before, the wait was for update of last_committed_sub_id, which happens a
bit earlier, and could leave worker threads potentially accessing bits of
the replication state that is no longer valid after slave stop.
- Fix a couple of places where the test suite would kill a thread waiting
inside enter_cond() in connection with debug_sync; debug_sync + kill can
crash in rare cases due to a race with mysys_var_current_mutex in this
case.
- Fix some corner cases where we had enter_cond() but no exit_cond().
- Fix that we could get failure in wait_for_prior_commit() but forget to flag
the error with my_error().
- Fix slave stop (both for normal stop and stop due to error). Now, at stop
we pick a specific safe point (in terms of event groups executed) and make
sure that all event groups before that point are executed to completion,
and that no event group after start executing; this ensures a safe place to
restart replication, even for non-transactional stuff/DDL. In error stop,
make sure that all prior event groups are allowed to execute to completion,
and that any later event groups that have started are rolled back, if
possible. The old code could leave eg. T1 and T3 committed but T2 not, or
it could even leave half a transaction not rolled back in some random
worker, which would cause big problems when that worker was later reused
after slave restart.
- Fix the accounting of amount of events queued for one worker. Before, the
amount was reduced immediately as soon as the events were dequeued (which
happens all at once); this allowed twice the amount of events to be queued
in memory for each single worker, which is not what users would expect.
- Fix that an error set during execution of one event was sometimes not
cleared before executing the next, causing problems with the error
reporting.
- Fix incorrect handling of thd->killed in worker threads.
2014-02-26 15:02:09 +01:00
|
|
|
|
|
|
|
e= this->parallel_entry;
|
|
|
|
mysql_mutex_lock(&e->LOCK_parallel_entry);
|
2015-01-07 14:45:39 +01:00
|
|
|
mark_start_commit_inner(e, gco, this);
|
MDEV-5657: Parallel replication.
Clean up and improve the parallel implementation code, mainly related to
scheduling of work to threads and handling of stop and errors.
Fix a lot of bugs in various corner cases that could lead to crashes or
corruption.
Fix that a single replication domain could easily grab all worker threads and
stall all other domains; now a configuration variable
--slave-domain-parallel-threads allows to limit the number of
workers.
Allow next event group to start as soon as previous group begins the commit
phase (as opposed to when it ends it); this allows multiple event groups on
the slave to participate in group commit, even when no other opportunities for
parallelism are available.
Various fixes:
- Fix some races in the rpl.rpl_parallel test case.
- Fix an old incorrect assertion in Log_event iocache read.
- Fix repeated malloc/free of wait_for_commit and rpl_group_info objects.
- Simplify wait_for_commit wakeup logic.
- Fix one case in queue_for_group_commit() where killing one thread would
fail to correctly signal the error to the next, causing loss of the
transaction after slave restart.
- Fix leaking of pthreads (and their allocated stack) due to missing
PTHREAD_CREATE_DETACHED attribute.
- Fix how one batch of group-committed transactions wait for the previous
batch before starting to execute themselves. The old code had a very
complex scheduling where the first transaction was handled differently,
with subtle bugs in corner cases. Now each event group is always scheduled
for a new worker (in a round-robin fashion amongst available workers).
Keep a count of how many transactions have started to commit, and wait for
that counter to reach the appropriate value.
- Fix slave stop to wait for all workers to actually complete processing;
before, the wait was for update of last_committed_sub_id, which happens a
bit earlier, and could leave worker threads potentially accessing bits of
the replication state that is no longer valid after slave stop.
- Fix a couple of places where the test suite would kill a thread waiting
inside enter_cond() in connection with debug_sync; debug_sync + kill can
crash in rare cases due to a race with mysys_var_current_mutex in this
case.
- Fix some corner cases where we had enter_cond() but no exit_cond().
- Fix that we could get failure in wait_for_prior_commit() but forget to flag
the error with my_error().
- Fix slave stop (both for normal stop and stop due to error). Now, at stop
we pick a specific safe point (in terms of event groups executed) and make
sure that all event groups before that point are executed to completion,
and that no event group after start executing; this ensures a safe place to
restart replication, even for non-transactional stuff/DDL. In error stop,
make sure that all prior event groups are allowed to execute to completion,
and that any later event groups that have started are rolled back, if
possible. The old code could leave eg. T1 and T3 committed but T2 not, or
it could even leave half a transaction not rolled back in some random
worker, which would cause big problems when that worker was later reused
after slave restart.
- Fix the accounting of amount of events queued for one worker. Before, the
amount was reduced immediately as soon as the events were dequeued (which
happens all at once); this allowed twice the amount of events to be queued
in memory for each single worker, which is not what users would expect.
- Fix that an error set during execution of one event was sometimes not
cleared before executing the next, causing problems with the error
reporting.
- Fix incorrect handling of thd->killed in worker threads.
2014-02-26 15:02:09 +01:00
|
|
|
mysql_mutex_unlock(&e->LOCK_parallel_entry);
|
|
|
|
}
|
|
|
|
|
|
|
|
|
2014-06-25 15:17:03 +02:00
|
|
|
/*
|
|
|
|
Format the current GTID as a string suitable for printing in error messages.
|
|
|
|
|
|
|
|
The string is stored in a buffer inside rpl_group_info, so remains valid
|
|
|
|
until next call to gtid_info() or until destruction of rpl_group_info.
|
|
|
|
|
|
|
|
If no GTID is available, then NULL is returned.
|
|
|
|
*/
|
|
|
|
char *
|
|
|
|
rpl_group_info::gtid_info()
|
|
|
|
{
|
|
|
|
if (!gtid_sub_id || !current_gtid.seq_no)
|
|
|
|
return NULL;
|
|
|
|
my_snprintf(gtid_info_buf, sizeof(gtid_info_buf), "Gtid %u-%u-%llu",
|
|
|
|
current_gtid.domain_id, current_gtid.server_id,
|
|
|
|
current_gtid.seq_no);
|
|
|
|
return gtid_info_buf;
|
|
|
|
}
|
|
|
|
|
|
|
|
|
MDEV-5262, MDEV-5914, MDEV-5941, MDEV-6020: Deadlocks during parallel
replication causing replication to fail.
In parallel replication, we run transactions from the master in parallel, but
force them to commit in the same order they did on the master. If we force T1
to commit before T2, but T2 holds eg. a row lock that is needed by T1, we get
a deadlock when T2 waits until T1 has committed.
Usually, we do not run T1 and T2 in parallel if there is a chance that they
can have conflicting locks like this, but there are certain edge cases where
it can occasionally happen (eg. MDEV-5914, MDEV-5941, MDEV-6020). The bug was
that this would cause replication to hang, eventually getting a lock timeout
and causing the slave to stop with error.
With this patch, InnoDB will report back to the upper layer whenever a
transactions T1 is about to do a lock wait on T2. If T1 and T2 are parallel
replication transactions, and T2 needs to commit later than T1, we can thus
detect the deadlock; we then kill T2, setting a flag that causes it to catch
the kill and convert it to a deadlock error; this error will then cause T2 to
roll back and release its locks (so that T1 can commit), and later T2 will be
re-tried and eventually also committed.
The kill happens asynchroneously in a slave background thread; this is
necessary, as the reporting from InnoDB about lock waits happen deep inside
the locking code, at a point where it is not possible to directly call
THD::awake() due to mutexes held.
Deadlock is assumed to be (very) rarely occuring, so this patch tries to
minimise the performance impact on the normal case where no deadlocks occur,
rather than optimise the handling of the occasional deadlock.
Also fix transaction retry due to deadlock when it happens after a transaction
already signalled to later transactions that it started to commit. In this
case we need to undo this signalling (and later redo it when we commit again
during retry), so following transactions will not start too early.
Also add a missing thd->send_kill_message() that got triggered during testing
(this corrects an incorrect fix for MySQL Bug#58933).
2014-06-03 10:31:11 +02:00
|
|
|
/*
|
|
|
|
Undo the effect of a prior mark_start_commit().
|
|
|
|
|
|
|
|
This is only used for retrying a transaction in parallel replication, after
|
|
|
|
we have encountered a deadlock or other temporary error.
|
|
|
|
|
|
|
|
When we get such a deadlock, it means that the current group of transactions
|
|
|
|
did not yet all start committing (else they would not have deadlocked). So
|
|
|
|
we will not yet have woken up anything in the next group, our rgi->gco is
|
|
|
|
still live, and we can simply decrement the counter (to be incremented again
|
|
|
|
later, when the retry succeeds and reaches the commit step).
|
|
|
|
*/
|
|
|
|
void
|
|
|
|
rpl_group_info::unmark_start_commit()
|
|
|
|
{
|
|
|
|
rpl_parallel_entry *e;
|
|
|
|
|
|
|
|
if (!did_mark_start_commit)
|
|
|
|
return;
|
2016-08-22 09:16:00 +02:00
|
|
|
did_mark_start_commit= false;
|
MDEV-5262, MDEV-5914, MDEV-5941, MDEV-6020: Deadlocks during parallel
replication causing replication to fail.
In parallel replication, we run transactions from the master in parallel, but
force them to commit in the same order they did on the master. If we force T1
to commit before T2, but T2 holds eg. a row lock that is needed by T1, we get
a deadlock when T2 waits until T1 has committed.
Usually, we do not run T1 and T2 in parallel if there is a chance that they
can have conflicting locks like this, but there are certain edge cases where
it can occasionally happen (eg. MDEV-5914, MDEV-5941, MDEV-6020). The bug was
that this would cause replication to hang, eventually getting a lock timeout
and causing the slave to stop with error.
With this patch, InnoDB will report back to the upper layer whenever a
transactions T1 is about to do a lock wait on T2. If T1 and T2 are parallel
replication transactions, and T2 needs to commit later than T1, we can thus
detect the deadlock; we then kill T2, setting a flag that causes it to catch
the kill and convert it to a deadlock error; this error will then cause T2 to
roll back and release its locks (so that T1 can commit), and later T2 will be
re-tried and eventually also committed.
The kill happens asynchroneously in a slave background thread; this is
necessary, as the reporting from InnoDB about lock waits happen deep inside
the locking code, at a point where it is not possible to directly call
THD::awake() due to mutexes held.
Deadlock is assumed to be (very) rarely occuring, so this patch tries to
minimise the performance impact on the normal case where no deadlocks occur,
rather than optimise the handling of the occasional deadlock.
Also fix transaction retry due to deadlock when it happens after a transaction
already signalled to later transactions that it started to commit. In this
case we need to undo this signalling (and later redo it when we commit again
during retry), so following transactions will not start too early.
Also add a missing thd->send_kill_message() that got triggered during testing
(this corrects an incorrect fix for MySQL Bug#58933).
2014-06-03 10:31:11 +02:00
|
|
|
|
|
|
|
e= this->parallel_entry;
|
|
|
|
mysql_mutex_lock(&e->LOCK_parallel_entry);
|
|
|
|
--e->count_committing_event_groups;
|
|
|
|
mysql_mutex_unlock(&e->LOCK_parallel_entry);
|
|
|
|
}
|
|
|
|
|
|
|
|
|
2014-04-25 12:58:31 +02:00
|
|
|
rpl_sql_thread_info::rpl_sql_thread_info(Rpl_filter *filter)
|
|
|
|
: rpl_filter(filter)
|
|
|
|
{
|
|
|
|
cached_charset_invalidate();
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
void rpl_sql_thread_info::cached_charset_invalidate()
|
|
|
|
{
|
|
|
|
DBUG_ENTER("rpl_group_info::cached_charset_invalidate");
|
|
|
|
|
|
|
|
/* Full of zeroes means uninitialized. */
|
|
|
|
bzero(cached_charset, sizeof(cached_charset));
|
|
|
|
DBUG_VOID_RETURN;
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
bool rpl_sql_thread_info::cached_charset_compare(char *charset) const
|
|
|
|
{
|
|
|
|
DBUG_ENTER("rpl_group_info::cached_charset_compare");
|
|
|
|
|
|
|
|
if (memcmp(cached_charset, charset, sizeof(cached_charset)))
|
|
|
|
{
|
|
|
|
memcpy(const_cast<char*>(cached_charset), charset, sizeof(cached_charset));
|
|
|
|
DBUG_RETURN(1);
|
|
|
|
}
|
|
|
|
DBUG_RETURN(0);
|
|
|
|
}
|
|
|
|
|
2016-09-22 13:36:45 +02:00
|
|
|
|
|
|
|
/**
|
|
|
|
Store the file and position where the slave's SQL thread are in the
|
|
|
|
relay log.
|
|
|
|
|
|
|
|
Notes:
|
|
|
|
|
|
|
|
- This function should be called either from the slave SQL thread,
|
|
|
|
or when the slave thread is not running. (It reads the
|
|
|
|
group_{relay|master}_log_{pos|name} and delay fields in the rli
|
|
|
|
object. These may only be modified by the slave SQL thread or by
|
|
|
|
a client thread when the slave SQL thread is not running.)
|
|
|
|
|
|
|
|
- If there is an active transaction, then we do not update the
|
|
|
|
position in the relay log. This is to ensure that we re-execute
|
|
|
|
statements if we die in the middle of an transaction that was
|
|
|
|
rolled back.
|
|
|
|
|
|
|
|
- As a transaction never spans binary logs, we don't have to handle
|
|
|
|
the case where we do a relay-log-rotation in the middle of the
|
|
|
|
transaction. If transactions could span several binlogs, we would
|
|
|
|
have to ensure that we do not delete the relay log file where the
|
|
|
|
transaction started before switching to a new relay log file.
|
|
|
|
|
|
|
|
- Error can happen if writing to file fails or if flushing the file
|
|
|
|
fails.
|
|
|
|
|
|
|
|
@param rli The object representing the Relay_log_info.
|
|
|
|
|
|
|
|
@todo Change the log file information to a binary format to avoid
|
|
|
|
calling longlong2str.
|
|
|
|
|
|
|
|
@return 0 on success, 1 on error.
|
|
|
|
*/
|
|
|
|
bool Relay_log_info::flush()
|
|
|
|
{
|
|
|
|
bool error=0;
|
|
|
|
|
|
|
|
DBUG_ENTER("Relay_log_info::flush()");
|
|
|
|
|
|
|
|
IO_CACHE *file = &info_file;
|
|
|
|
// 2*file name, 2*long long, 2*unsigned long, 6*'\n'
|
|
|
|
char buff[FN_REFLEN * 2 + 22 * 2 + 10 * 2 + 6], *pos;
|
|
|
|
my_b_seek(file, 0L);
|
|
|
|
pos= longlong10_to_str(LINES_IN_RELAY_LOG_INFO_WITH_DELAY, buff, 10);
|
|
|
|
*pos++='\n';
|
|
|
|
pos=strmov(pos, group_relay_log_name);
|
|
|
|
*pos++='\n';
|
|
|
|
pos=longlong10_to_str(group_relay_log_pos, pos, 10);
|
|
|
|
*pos++='\n';
|
|
|
|
pos=strmov(pos, group_master_log_name);
|
|
|
|
*pos++='\n';
|
|
|
|
pos=longlong10_to_str(group_master_log_pos, pos, 10);
|
|
|
|
*pos++='\n';
|
|
|
|
pos= longlong10_to_str(sql_delay, pos, 10);
|
|
|
|
*pos++= '\n';
|
|
|
|
if (my_b_write(file, (uchar*) buff, (size_t) (pos-buff)))
|
|
|
|
error=1;
|
|
|
|
if (flush_io_cache(file))
|
|
|
|
error=1;
|
|
|
|
if (sync_relayloginfo_period &&
|
|
|
|
!error &&
|
|
|
|
++sync_counter >= sync_relayloginfo_period)
|
|
|
|
{
|
|
|
|
if (my_sync(info_fd, MYF(MY_WME)))
|
|
|
|
error=1;
|
|
|
|
sync_counter= 0;
|
|
|
|
}
|
|
|
|
/*
|
|
|
|
Flushing the relay log is done by the slave I/O thread
|
|
|
|
or by the user on STOP SLAVE.
|
|
|
|
*/
|
|
|
|
DBUG_RETURN(error);
|
|
|
|
}
|
|
|
|
|
2006-10-31 12:23:14 +01:00
|
|
|
#endif
|