[MDEV-26483] rpl.rpl_semi_sync_fail_over failed in bb, FOUND 1 /truncated binlog Created: 2021-08-26  Updated: 2023-06-23

Status: Open
Project: MariaDB Server
Component/s: Replication, Tests
Affects Version/s: 10.6, 10.7
Fix Version/s: 10.6

Type: Bug Priority: Major
Reporter: Alice Sherepa Assignee: Andrei Elkin
Resolution: Unresolved Votes: 0
Labels: None

Attachments: Text File build8256_mysqld.1.err.12.txt     Text File build8256_mysqld.2.err.12.txt    

 Description   

http://buildbot.askmonty.org/buildbot/builders/kvm-fulltest2/builds/30422/steps/mtr_nm/logs/stdio

rpl.rpl_semi_sync_fail_over 'innodb,row' w3 [ fail ]
 
        Test ended at 2021-08-23 08:35:24
 
 
 
CURRENT_TEST: rpl.rpl_semi_sync_fail_over
 
--- /mnt/buildbot/build/mariadb-10.7.0/mysql-test/suite/rpl/r/rpl_semi_sync_fail_over.result	2021-08-23 04:54:38.000000000 -0400
 
+++ /mnt/buildbot/build/mariadb-10.7.0/mysql-test/suite/rpl/r/rpl_semi_sync_fail_over.reject	2021-08-23 08:35:24.701239025 -0400
 
@@ -196,7 +196,7 @@
 
 # restart: --skip-slave-start=1 --rpl-semi-sync-slave-enabled=1
 
 connection server_1;
 
 include/assert.inc [Table t1 should have 6 rows.]
 
-NOT FOUND /truncated binlog file:.*master.*000003/ in mysqld.1.err
 
+FOUND 1 /truncated binlog file:.*master.*000003/ in mysqld.1.err
 
 disconnect conn_client;
 
 connection server_2;
 
 set global rpl_semi_sync_master_enabled = 1;
 
 
 
mysqltest: Result length mismatch



 Comments   
Comment by Alice Sherepa [ 2021-09-17 ]

also on 10.6 https://buildbot.mariadb.org/#/builders/192/builds/4796/steps/6/logs/stdio

Comment by Alice Sherepa [ 2021-11-03 ]

on 10.8 https://buildbot.askmonty.org/buildbot/builders/kvm-fulltest2/builds/31869/steps/mtr_nm/logs/stdio

Comment by Angelique Sklavounos (Inactive) [ 2022-03-09 ]

On 10.9 35fcae10408aa4c54967d118c8ccde1c3736b85f https://buildbot.mariadb.org/#/builders/192/builds/8256/steps/6/logs/stdio

Primary and replica logs attached as build8256_mysqld.[12].err.12.txt
build8256_mysqld.1.err.12.txt build8256_mysqld.2.err.12.txt

Comment by Alice Sherepa [ 2023-06-23 ]

Currently test fails in a different way:
https://buildbot.mariadb.net/buildbot/builders/kvm-fulltest2/builds/41455/steps/mtr_nm/logs/stdio

rpl.rpl_semi_sync_fail_over 'innodb,row' w1 [ fail ]
 
        Test ended at 2023-06-07 19:02:36
 
 
 
CURRENT_TEST: rpl.rpl_semi_sync_fail_over
 
mysqltest: In included file "./include/assert.inc": 
included from /mnt/buildbot/build/mariadb-10.9.8/mysql-test/suite/rpl/t/rpl_semi_sync_crash.inc at line 74:
 
included from /mnt/buildbot/build/mariadb-10.9.8/mysql-test/suite/rpl/t/rpl_semi_sync_fail_over.test at line 117:
 
At line 168: Test assertion failed in assertion.inc
 
 
 
The result from queries just before the failure was:
 
< snip >
 
master-bin.000002	4896	Gtid	1	4938	BEGIN GTID 0-1-6
 
master-bin.000002	4938	Annotate_rows	1	5035	SET STATEMENT server_id=1 FOR INSERT INTO t1 VALUES (4, REPEAT("x", 4100))
 
master-bin.000002	5035	Table_map	1	5082	table_id: 18 (test.t1)
 
master-bin.000002	5082	Write_rows_v1	1	9223	table_id: 18 flags: STMT_END_F
 
master-bin.000002	9223	Xid	1	9254	COMMIT /* xid=108 */
 
 
 
**** SHOW RELAYLOG EVENTS on server_1 ****
 
relaylog_name = 'master-relay-bin.000006'
 
SHOW RELAYLOG EVENTS IN 'master-relay-bin.000006';
 
Log_name	Pos	Event_type	Server_id	End_log_pos	Info
 
master-relay-bin.000006	4	Format_desc	1	256	Server ver: 10.9.8-MariaDB-debug-log, Binlog ver: 4
 
master-relay-bin.000006	256	Rotate	2	0	slave-bin.000003;pos=4
 
master-relay-bin.000006	303	Format_desc	2	256	Server ver: 10.9.8-MariaDB-debug-log, Binlog ver: 4
 
master-relay-bin.000006	555	Gtid_list	2	315	[0-2-5,0-1-6]
 
master-relay-bin.000006	614	Binlog_checkpoint	2	358	slave-bin.000002
 
connection server_1;
 
Assertion text: 'Table t1 should have 5 rows.'
 
Assertion condition: 'COUNT(*) = 5 FROM t1'
 
Assertion condition, interpolated: 'COUNT(*) = 5 FROM t1'
 
Assertion result: '0'
 
 
 
More results from queries before failure can be found in /mnt/buildbot/build/mariadb-10.9.8/mysql-test/var/1/log/rpl_semi_sync_fail_over.log

Generated at Thu Feb 08 09:45:39 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.