[MDEV-17948] Assertion `thd_killed(thd) || !m_active_tranxs || !m_active_tranxs->is_tranx_end_pos(trx_wait_binlog_name, trx_wait_binlog_pos)' failed in Repl_semi_sync_master::commit_trx Created: 2018-12-09  Updated: 2020-11-04  Resolved: 2019-05-24

Status: Closed
Project: MariaDB Server
Component/s: Replication
Affects Version/s: 10.1, 10.2, 10.3, 10.4
Fix Version/s: 10.2.25, 10.1.41, 10.3.16, 10.4.6

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Andrei Elkin
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Duplicate
is duplicated by MDEV-24120 Assertion `thd_killed(current_thd) ||... Confirmed
Relates
relates to MDEV-19376 Repl_semi_sync_master::commit_trx ass... Closed

 Description    

--source include/master-slave.inc
 
 
 
SET @@GLOBAL.rpl_semi_sync_master_enabled = 1;
 
 
 
--connection slave
 
source include/stop_slave.inc;
 
SET @@GLOBAL. rpl_semi_sync_slave_enabled = 1;
 
source include/start_slave.inc;
 
 
 
--connection master
 
SET @@GLOBAL.debug_dbug= "d,dbug_master_binlog_over_2GB";
 
CREATE TABLE t1 (a INT);
 
INSERT INTO t1 SET a=0;
 
 
 
--sync_slave_with_master

The test case is derived from rpl.rpl_semi_sync_skip_repl . I would think that maybe the debug injection causes it intentionally, but since the failure only happens with semisync enabled, I suspect there might be a problem.

Not reproducible on 10.0.

 Comments   
Comment by Andrei Elkin [ 2019-05-23 ]

julien.fritsch I crossed a test failure while was working on MDEV-7974 and got to dwell into it (naturally with the idea of clearing off my MDEV) to latter find out
that it's the test's fault and has nothing to do with my MDEV, and that there's an open bug mentioning the test.
The total work therefore as it often happens with test failures consists of 2/3 of analysis and 1/3 of the test refinement. I could've left out the fixing part, but that about 1 hr.

I hope this clarifies and justifies.

Cheers.

Comment by Andrei Elkin [ 2019-05-24 ]

A pure test changes patch aaf53ea0b68 is pushed to 10.1.

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