mirror of
https://github.com/MariaDB/server.git
synced 2025-01-19 05:22:25 +01:00
f8b64e17f9
using TPC-B): Problem: A RBR event can contain incomplete row data (only key value and fields which have been changed). In that case, when the row is unpacked into record and written to a table, the missing fields get incorrect NULL values leading to master-slave inconsistency. Solution: Use values found in slave's table for columns which are not given in the rows event. The code for writing a single row uses the following algorithm: 1. unpack row_data into table->record[0], 2. try to insert record, 3. if duplicate record found, fetch it into table->record[0], 4. unpack row_data into table->record[0], 5. write table->record[0] into the table. Where row_data is the row as stored in the data area of a rows event. Thus: a) unpacking of row_data happens at the time when row is written into a table, b) when unpacking (in step 4), only columns present in row_data are overwritten - all other columns remain as they were found in the table. Since all data needed for the above algorithm is stored inside Rows_log_event class, functions which locate and write rows are turned into methods of that class. replace_record() -> Rows_log_event::write_row() find_and_fetch_row() -> Rows_log_event::find_row() Both methods take row data from event's data buffer - the row being processed is pointed by m_curr_row. They unpack the data as needed into table's record buffers record[0] or record[1]. When row is unpacked, m_curr_row_end is set to point at next row in the data buffer. Other changes introduced in this changeset: - Change signature of unpack_row(): don't report errors and don't setup table's rw_set here. Errors can happen only when setting default values in prepare_record() function and are detected there. - In Rows_log_event and derived classes, don't pass arguments to the execution primitives (do_...() member functions) but use class members instead. - Move old row handling code into log_event_old.cc to be used by *_rows_log_event_old classes. Also, a new test rpl_ndb_2other is added which tests basic replication from master using ndb tables to slave storing the same tables using (possibly) different engine (myisam,innodb). Test is based on existing tests rpl_ndb_2myisam and rpl_ndb_2innodb. However, these tests doesn't work for various reasons and currently are disabled (see BUG#19227). The new test differs from the ones it is based on as follows: 1. Single test tests replication with different storage engines on slave (myisam, innodb, ndb). 2. Include file extra/rpl_tests/rpl_ndb_2multi_eng.test containing original tests is replaced by extra/rpl_tests/rpl_ndb_2multi_basic.test which doesn't contain tests using partitioned tables as these don't work currently. Instead, it tests replication to a slave which has more or less columns than master. 3. Include file include/rpl_multi_engine3.inc is replaced with include/rpl_multi_engine2.inc. The later differs by performing slightly different operations (updating more than one row in the table) and clearing table with "TRUNCATE TABLE" statement instead of "DELETE FROM" as replication of "DELETE" doesn't work well in this setting. 4. Slave must use option --log-slave-updates=0 as otherwise execution of replication events generated by ndb fails if table uses a different storage engine on slave (see BUG#29569).
91 lines
2.6 KiB
SQL
91 lines
2.6 KiB
SQL
#############################################################
|
|
# Author: Rafal
|
|
# Date: 2007-08-20
|
|
# based on rpl_multi_engine3.inc
|
|
#############################################################
|
|
|
|
connection slave;
|
|
STOP SLAVE;
|
|
RESET SLAVE;
|
|
|
|
connection master;
|
|
RESET MASTER;
|
|
|
|
connection slave;
|
|
START SLAVE;
|
|
|
|
--echo --- Populate t1 with data ---
|
|
connection master;
|
|
--disable_query_log
|
|
INSERT INTO t1 VALUES(42,1,'Testing MySQL databases is a cool ',
|
|
'Must make it bug free for the customer',
|
|
654321.4321,15.21,0,1965,"1905-11-14");
|
|
INSERT INTO t1 VALUES(2,1,'Testing MySQL databases is a cool ',
|
|
'Must make it bug free for the customer',
|
|
654321.4321,15.21,0,1965,"1965-11-14");
|
|
INSERT INTO t1 VALUES(4,1,'Testing MySQL databases is a cool ',
|
|
'Must make it bug free for the customer',
|
|
654321.4321,15.21,0,1965,"1985-11-14");
|
|
INSERT INTO t1 VALUES(142,1,'Testing MySQL databases is a cool ',
|
|
'Must make it bug free for the customer',
|
|
654321.4321,15.21,0,1965,"1995-11-14");
|
|
INSERT INTO t1 VALUES(412,1,'Testing MySQL databases is a cool ',
|
|
'Must make it bug free for the customer',
|
|
654321.4321,15.21,0,1965,"2005-11-14");
|
|
--enable_query_log
|
|
|
|
--echo --- Select from t1 on master ---
|
|
select *
|
|
from t1
|
|
order by id;
|
|
|
|
sync_slave_with_master;
|
|
--echo --- Select from t1 on slave ---
|
|
select *
|
|
from t1
|
|
order by id;
|
|
|
|
--echo --- Perform basic operation on master ---
|
|
--echo --- and ensure replicated correctly ---
|
|
connection master;
|
|
|
|
--echo --- Update t1 on master --
|
|
UPDATE t1 SET b1 = 0, bc='updated', t="2006-02-22"
|
|
WHERE id < 100
|
|
ORDER BY id;
|
|
|
|
--echo --- Check the update on master ---
|
|
SELECT *
|
|
FROM t1
|
|
WHERE id < 100
|
|
ORDER BY id;
|
|
|
|
# Must give injector thread a little time to get update
|
|
# into the binlog other wise we will miss the update.
|
|
|
|
sync_slave_with_master;
|
|
--echo --- Check Update on slave ---
|
|
SELECT *
|
|
FROM t1
|
|
WHERE id < 100
|
|
ORDER BY id;
|
|
|
|
connection master;
|
|
--echo --- Remove a record from t1 on master ---
|
|
# Note: there is an error in replication of Delete_row
|
|
# from NDB to MyISAM (BUG#28538). However, if there is
|
|
# only one row in Delete_row event then it works fine,
|
|
# as this test demonstrates.
|
|
DELETE FROM t1 WHERE id = 412;
|
|
|
|
--echo --- Show current count on master for t1 ---
|
|
SELECT COUNT(*) FROM t1;
|
|
|
|
sync_slave_with_master;
|
|
--echo --- Show current count on slave for t1 ---
|
|
SELECT COUNT(*) FROM t1;
|
|
|
|
connection master;
|
|
TRUNCATE TABLE t1;
|
|
sync_slave_with_master;
|
|
connection master;
|