[MDEV-19746] Galera test failures because of wsrep_slave_threads identification Created: 2019-06-13  Updated: 2019-12-18  Resolved: 2019-07-16

Status: Closed
Project: MariaDB Server
Component/s: Galera, Tests
Affects Version/s: 10.2, 10.3, 10.4
Fix Version/s: 10.2.26, 10.3.17, 10.4.7

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


 Description   

Effected tests

  • wsrep.variables
  • MW-366
  • galera_var_slave_threads
  • galera_parallel_autoinc_manytrx
  • galera_parallel_autoinc_largetrx
  • galera_kill_applier


 Comments   
Comment by Jan Lindström (Inactive) [ 2019-06-13 ]

wsrep.variables                          w1 [ fail ]
        Test ended at 2019-06-12 13:03:08
 
CURRENT_TEST: wsrep.variables
--- /usr/share/mysql-test/suite/wsrep/r/variables.result	2019-06-12 10:37:18.000000000 +0300
+++ /dev/shm/var/1/log/variables.reject	2019-06-12 13:03:07.806336541 +0300
@@ -149,12 +149,27 @@
 SET @wsrep_slave_threads_saved= @@global.wsrep_slave_threads;
 SET GLOBAL wsrep_slave_threads= 10;
 # Wait for applier threads to get created.
+Timeout in wait_condition.inc for SELECT COUNT(*) = 11 FROM INFORMATION_SCHEMA.PROCESSLIST WHERE USER = 'system user' AND (STATE IS NULL OR STATE NOT LIKE 'InnoDB%');
+Id	User	Host	db	Command	Time	State	Info	Progress
+12	root	localhost	test	Query	0	init	show full processlist	0.000
+13	system user		NULL	Sleep	30	wsrep aborter idle	NULL	0.000
+14	system user		NULL	Sleep	30	NULL	NULL	0.000
+15	system user		NULL	Sleep	30	NULL	NULL	0.000
+24	system user		NULL	Sleep	30	NULL	NULL	0.000
+18	system user		NULL	Sleep	30	NULL	NULL	0.000
+19	system user		NULL	Sleep	30	NULL	NULL	0.000
+17	system user		NULL	Sleep	30	NULL	NULL	0.000
+21	system user		NULL	Sleep	30	NULL	NULL	0.000
+20	system user		NULL	Sleep	30	NULL	NULL	0.000
+16	system user		NULL	Sleep	30	NULL	NULL	0.000
+22	system user		NULL	Sleep	30	NULL	NULL	0.000
+23	system user		NULL	Sleep	30	NULL	NULL	0.000

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