[MDEV-18179] Galera test failure on galera.galera_kill_largechanges Created: 2019-01-09  Updated: 2022-10-22  Resolved: 2022-05-23

Status: Closed
Project: MariaDB Server
Component/s: Galera, Tests
Affects Version/s: 10.4
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Jan Lindström (Inactive) Assignee: Jan Lindström (Inactive)
Resolution: Cannot Reproduce Votes: 0
Labels: Test_disabled, need_verification, test_disabled_ES


 Description   

galera.galera_kill_largechanges 'innodb' w1 [ fail ]
        Test ended at 2019-01-09 09:16:26
 
CURRENT_TEST: galera.galera_kill_largechanges
mysqltest: In included file "./include/galera_wait_ready.inc": 
included from /home/jan/mysql/10.4-galera-2/mysql-test/suite/galera/include/start_mysqld.inc at line 16:
included from /home/jan/mysql/10.4-galera-2/mysql-test/suite/galera/t/galera_kill_largechanges.test at line 30:
At line 28: "Server did not transition to READY state"
 
The result from queries just before the failure was:
connection node_2;
connection node_1;
call mtr.add_suppression("WSREP: Last Applied Action message in non-primary configuration from member .*");
connection node_1;
SET GLOBAL wsrep_provider_options = 'pc.ignore_sb=true';
CREATE TABLE ten (f1 INTEGER);
INSERT INTO ten VALUES (1), (2), (3), (4), (5), (6), (7), (8), (9), (10);
CREATE TABLE t1 (f1 VARCHAR(128)) ENGINE=InnoDB;
connection node_2;
Killing server ...
connection node_1;
INSERT INTO t1 SELECT REPEAT('a', 128) FROM ten AS a1, ten AS a2, ten AS a3, ten AS a4, ten AS a5, ten AS a6;
connection node_2;



 Comments   
Comment by Jan Lindström (Inactive) [ 2022-05-23 ]

Could not reproduce with latest 10.4+26.4.12 but I will remove this test as it is very slow.

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