[MDEV-21308] WSREP: binlog ... cache not empty warnings on server with WSREP disabled Created: 2019-12-12  Updated: 2022-01-22  Resolved: 2022-01-22

Status: Closed
Project: MariaDB Server
Component/s: wsrep
Affects Version/s: 10.1, 10.2, 10.3, 10.4
Fix Version/s: 10.2.42, 10.3.33, 10.4.23, 10.5.14, 10.6.6, 10.7.2

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Jan Lindström (Inactive)
Resolution: Fixed Votes: 0
Labels: None


 Description   

--source include/have_innodb.inc
--source include/have_binlog_format_row.inc
 
CREATE TABLE t1 (a INT) ENGINE=InnoDB;
CREATE TABLE t2 (b INT) ENGINE=InnoDB;
CREATE TABLE t3 (c INT) ENGINE=InnoDB;
CREATE TRIGGER tr1 BEFORE INSERT ON t3 FOR EACH ROW INSERT INTO t2 VALUES (NULL) ; 
CREATE TRIGGER tr2 BEFORE UPDATE ON t2 FOR EACH ROW SET @a = 1; 
 
LOCK TABLE t3 WRITE;
SET AUTOCOMMIT = OFF;
INSERT INTO t2 VALUES (1);
SAVEPOINT A;
UNLOCK TABLES;
INSERT INTO t1 VALUES (2);
 
# Cleanup
DROP TABLE t1, t2, t3;

10.4 non-debug 3b401a69

 

line
2019-12-12 16:17:52 10 [Warning] WSREP: binlog trx cache not empty (34 bytes) @ connection close 10
2019-12-12 16:17:52 10 [Warning] WSREP: binlog stmt cache not empty (0 bytes) @ connection close 10
^ Found warnings in /data/bld/10.4-rel-nightly/mysql-test/var/log/mysqld.1.err

 

Debug builds additionally fail with MDEV-21307.



 Comments   
Comment by Elena Stepanova [ 2019-12-12 ]

marko said on Slack:

Could we have a debug assertion inside of the WSREP_ spam primitives that asserts that wsrep is enabled? And do a validation run with RQG?

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