[MDEV-20840] innodb.undo_truncate sporadic timeout waiting for innodb_undo_truncations Created: 2019-10-16  Updated: 2020-10-05  Resolved: 2020-10-05

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

Type: Bug Priority: Critical
Reporter: Vladislav Vaintroub Assignee: Timofey Turenko
Resolution: Cannot Reproduce Votes: 0
Labels: need_feedback, need_rr


 Description   

from http://buildbot.askmonty.org/buildbot/builders/win32-debug/builds/15351

innodb.undo_truncate '16k,2,innodb' w2 [ fail ]
Test ended at 2019-09-11 01:32:16

CURRENT_TEST: innodb.undo_truncate
— D:/win32-debug/build/src/mysql-test/suite/innodb/r/undo_truncate.result 2019-09-11 01:20:32.641789900 +0000
+++ D:\win32-debug\build\src\mysql-test\suite\innodb\r\undo_truncate.reject 2019-09-11 01:32:15.829648600 +0000
@@ -55,6 +55,16 @@
drop PROCEDURE populate_t1;
drop PROCEDURE populate_t2;
InnoDB 0 transactions not purged
+Timeout in wait_condition.inc for (SELECT variable_value!=@trunc_start
+FROM information_schema.global_status
+WHERE variable_name = 'innodb_undo_truncations')
+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:62315 test Query 0 Init show full processlist 0.000
SET GLOBAL innodb_undo_logs = @save_undo_logs;
SET GLOBAL innodb_purge_rseg_truncate_frequency = @save_frequency;
SET GLOBAL innodb_undo_log_truncate = @save_truncate;



 Comments   
Comment by Vladislav Vaintroub [ 2019-10-16 ]

One more occurrence in http://buildbot.askmonty.org/buildbot/builders/winx64-packages/builds/15645

Comment by Timofey Turenko [ 2020-09-03 ]

I have not seen this since June. I guess it can be closed

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