[MDEV-22515] innodb.innodb_buffer_pool_resize_debug fails with timeout in wait_condition Created: 2020-05-09  Updated: 2023-05-16  Resolved: 2021-07-06

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB, Tests
Affects Version/s: 10.2, 10.3
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Marko Mäkelä
Resolution: Won't Fix Votes: 0
Labels: not-10.4, not-10.5, not-10.6


 Description   

The test fails reliably on, for example, ARM CentOS-7, 10.2 and 10.3. It used to fail on 10.4 too, see the output below, and it still fails on that revision, but not on current 10.4+. There is no difference in the test between 10.2 and 10.4, so something has been fixed in the server since then.

10.2 621fae3cbc

innodb.innodb_buffer_pool_resize_debug 'innodb' [ fail ]
        Test ended at 2021-07-06 22:07:14
 
CURRENT_TEST: innodb.innodb_buffer_pool_resize_debug
--- /home/buildbot/10.2/mysql-test/suite/innodb/r/innodb_buffer_pool_resize_debug.result	2021-07-06 19:01:14.705560602 +0000
+++ /home/buildbot/10.2/mysql-test/suite/innodb/r/innodb_buffer_pool_resize_debug.reject	2021-07-06 22:07:13.555069453 +0000
@@ -102,6 +102,16 @@
 set global innodb_disable_resize_buffer_pool_debug = OFF;
 set @before_innodb_buffer_pool_size = @@innodb_buffer_pool_size;
 set global innodb_buffer_pool_size=@before_innodb_buffer_pool_size;
+Timeout in wait_condition.inc for SELECT SUBSTR(variable_value, 1, 19) = 'Size did not change'
+  FROM information_schema.global_status
+WHERE VARIABLE_NAME = 'INNODB_BUFFER_POOL_RESIZE_STATUS'
+Id	User	Host	db	Command	Time	State	Info	Progress
+3	system user		NULL	Daemon	NULL	InnoDB purge worker	NULL	0.000
+1	system user		NULL	Daemon	NULL	InnoDB purge worker	NULL	0.000
+2	system user		NULL	Daemon	NULL	InnoDB purge coordinator	NULL	0.000
+4	system user		NULL	Daemon	NULL	InnoDB purge worker	NULL	0.000
+5	system user		NULL	Daemon	NULL	InnoDB shutdown handler	NULL	0.000
+9	root	localhost	test	Query	0	init	show full processlist	0.000
 set global innodb_buffer_pool_size=@before_innodb_buffer_pool_size * 2;
 set global innodb_buffer_pool_size=@before_innodb_buffer_pool_size;
 set global innodb_buffer_pool_size=@before_innodb_buffer_pool_size;
 
mysqltest: Result length mismatch


From the original report, old revision of 10.4:

http://buildbot.askmonty.org/buildbot/builders/bld-p9-rhel7/builds/3233

10.4 01f8f33b43e5aa63752ccd71a6a63c58

innodb.innodb_buffer_pool_resize_debug 'innodb' w50 [ fail ]
        Test ended at 2020-04-29 09:39:28
 
CURRENT_TEST: innodb.innodb_buffer_pool_resize_debug
--- /opt/buildbot-slave/bld-p9-rhel7/build/mysql-test/suite/innodb/r/innodb_buffer_pool_resize_debug.result	2020-04-29 09:33:08.704649459 +0300
+++ /opt/buildbot-slave/bld-p9-rhel7/build/mysql-test/suite/innodb/r/innodb_buffer_pool_resize_debug.reject	2020-04-29 09:39:27.929496056 +0300
@@ -102,6 +102,16 @@
 set global innodb_disable_resize_buffer_pool_debug = OFF;
 set @before_innodb_buffer_pool_size = @@innodb_buffer_pool_size;
 set global innodb_buffer_pool_size=@before_innodb_buffer_pool_size;
+Timeout in wait_condition.inc for SELECT SUBSTR(variable_value, 1, 19) = 'Size did not change'
+  FROM information_schema.global_status
+WHERE VARIABLE_NAME = 'INNODB_BUFFER_POOL_RESIZE_STATUS'
+Id	User	Host	db	Command	Time	State	Info	Progress
+1	system user		NULL	Daemon	NULL	InnoDB purge coordinator	NULL	0.000
+2	system user		NULL	Daemon	NULL	InnoDB purge worker	NULL	0.000
+3	system user		NULL	Daemon	NULL	InnoDB purge worker	NULL	0.000
+4	system user		NULL	Daemon	NULL	InnoDB purge worker	NULL	0.000
+5	system user		NULL	Daemon	NULL	InnoDB shutdown handler	NULL	0.000
+9	root	localhost	test	Query	0	init	show full processlist	0.000
 set global innodb_buffer_pool_size=@before_innodb_buffer_pool_size * 2;
 set global innodb_buffer_pool_size=@before_innodb_buffer_pool_size;
 set global innodb_buffer_pool_size=@before_innodb_buffer_pool_size;
 
mysqltest: Result length mismatch



 Comments   
Comment by Elena Stepanova [ 2021-07-06 ]

It must be the same problem as MDEV-25895, a problem with large pages.
If the non-debug version of the same issue was decided not important enough to fix, then the debug one is even less worthy, so I'm closing it as "Won't fix"

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