mirror of
https://github.com/MariaDB/server.git
synced 2025-12-18 10:22:14 +03:00
b347396181
Problem: ======= rpl_blackhole.test fails when executed with following options mysqld=--binlog_annotate_row_events=1, mysqld=--replicate_annotate_row_events=1 Test output: ------------ worker[1] Using MTR_BUILD_THREAD 300, with reserved ports 16000..16019 rpl.rpl_blackhole_bug 'mix' [ pass ] 791 rpl.rpl_blackhole_bug 'row' [ fail ] Replicate_Wild_Ignore_Table Last_Errno 1032 Last_Error Could not execute Update_rows_v1 event on table test.t1; Can't find record in 't1', Error_code: 1032; handler error HA_ERR_END_OF_FILE; the event's master log master-bin.000001, end_log_pos 1510 Analysis: ========= Enabling "replicate_annotate_row_events" on slave, Tells the slave to write annotate rows events received from the master to its own binary log. The received annotate events are applied after the Gtid event as shown below. thd->query() will be set to the actual query received from the master, through annotate event. Annotate_rows event should not be deleted after the event is applied as the thd->query will be used to generate new Annotate_rows event during applying the subsequent Rows events. After the last Rows event has been applied, the saved Annotate_rows event (if any) will be deleted. In balckhole engine all the DML operations are noops as they donot store any data. They simply return success without doing any operation. But the existing strictly expects thd->query() to be 'NULL' to identify that row based replication is in use. This assumption will fail when row annotations are enabled as the query is not 'NULL'. Hence various row based operations like 'update', 'delete', 'index lookup' will fail when row annotations are enabled. Fix: === Extend the row based replication check to include row annotations as well. i.e Either the thd->query() is NULL or thd->query() points to query and row annotations are in use.
50 lines
1.8 KiB
Plaintext
50 lines
1.8 KiB
Plaintext
# ==== Purpose ====
|
|
#
|
|
# Test verifies that when "replicate_annotate_row_events" are enabled on slave
|
|
# the DML operations on blackhole engine will be successful. It also ensures
|
|
# that Annotate events are logged into slave's binary log.
|
|
#
|
|
# ==== Implementation ====
|
|
#
|
|
# Steps:
|
|
# 0 - Enable "replicate_annotate_row_events" on slave and do DML operations
|
|
# on master.
|
|
# 1 - Slave server will successfully apply the DML operations and it is in
|
|
# sync with master.
|
|
# 2 - Verify that the "show binlog events" prints all annotate events.
|
|
# 3 - Stream the slave's binary log using "mysqlbinlog" tool and verify
|
|
# that the Annotate events are being displayed.
|
|
#
|
|
# ==== References ====
|
|
#
|
|
# MDEV-11094: Blackhole table updates on slave fail when row annotation is
|
|
# enabled
|
|
|
|
source include/have_blackhole.inc;
|
|
source include/have_binlog_format_row.inc;
|
|
source include/binlog_start_pos.inc;
|
|
source include/master-slave.inc;
|
|
|
|
SET timestamp=1000000000;
|
|
RESET MASTER;
|
|
connection slave;
|
|
SET timestamp=1000000000;
|
|
RESET MASTER;
|
|
|
|
connection master;
|
|
source extra/rpl_tests/rpl_blackhole_basic.test;
|
|
|
|
# Verify on slave.
|
|
connection slave;
|
|
FLUSH LOGS;
|
|
--replace_column 2 # 5 #
|
|
--replace_result $binlog_start_pos <start_pos>
|
|
--replace_regex /table_id: [0-9]+/table_id: #/ /\/\* xid=.* \*\//\/* xid= *\//
|
|
--eval show binlog events in 'slave-bin.000001' from $binlog_start_pos
|
|
|
|
let $MYSQLD_DATADIR= `select @@datadir`;
|
|
--replace_regex /server id [0-9]*/server id #/ /server v [^ ]*/server v #.##.##/ /exec_time=[0-9]*/exec_time=#/ /thread_id=[0-9]*/thread_id=#/ /table id [0-9]*/table id #/ /mapped to number [0-9]*/mapped to number #/ /end_log_pos [0-9]*/end_log_pos #/ /# at [0-9]*/# at #/
|
|
--exec $MYSQL_BINLOG --base64-output=decode-rows $MYSQLD_DATADIR/slave-bin.000001
|
|
|
|
source include/rpl_end.inc;
|