[MDEV-15405] Mixed replication fails with "Could not execute Delete_rows_v1 event" upon DELETE HISTORY Created: 2018-02-24  Updated: 2018-02-25  Resolved: 2018-02-25

Status: Closed
Project: MariaDB Server
Component/s: Replication, Versioned Tables
Affects Version/s: 10.3
Fix Version/s: 10.3.5

Type: Bug Priority: Critical
Reporter: Elena Stepanova Assignee: Sergei Golubchik
Resolution: Fixed Votes: 0
Labels: None


 Description   

--source include/have_binlog_format_mixed.inc
--source include/master-slave.inc
 
CREATE TABLE t1 (pk INT PRIMARY KEY, i INT) WITH SYSTEM VERSIONING;
INSERT INTO t1 VALUES (1,10),(2,20);
UPDATE t1 SET i = 100;
 
# This is to imitiate any real-life situation which causes a switch to row format
SET BINLOG_FORMAT= ROW;
 
DELETE HISTORY FROM t1;
 
--sync_slave_with_master

bb-10.3-release 9b59f78d16fb

2018-02-24 15:08:42 13 [ERROR] mysqld: Can't find record in 't1'
2018-02-24 15:08:42 13 [ERROR] Slave SQL: Could not execute Delete_rows_v1 event on table test.t1; Can't find record in 't1', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log master-bin.000001, end_log_pos 1140, Gtid 0-1-4, Internal MariaDB error code: 1032
2018-02-24 15:08:42 13 [Warning] Slave: Can't find record in 't1' Error_code: 1032
2018-02-24 15:08:42 13 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'master-bin.000001' position 924


Generated at Thu Feb 08 08:21:03 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.