[MDEV-22213] innodb.101_compatibility crashes with assert "mlog_checkpoint_lsn <= recovered_lsn" Created: 2020-04-10  Updated: 2020-06-02  Resolved: 2020-06-02

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

Type: Bug Priority: Major
Reporter: Michael Widenius Assignee: Thirunarayanan Balathandayuthapani
Resolution: Duplicate Votes: 0
Labels: None

Issue Links:
Duplicate
duplicates MDEV-13830 Assertion failed: recv_sys->mlog_chec... Closed
duplicates MDEV-22027 Assertion oldest_lsn >= log_sys.last_... Closed

 Description   

Windows build, test innodb.101_compatibility

Assertion failed: mlog_checkpoint_lsn <= recovered_lsn, file D:\winx64-debug\build\src\storage\innobase\log\log0recv.cc, line 2127
 
Server version: 10.5.3-MariaDB-debug-log
key_buffer_size=1048576
read_buffer_size=131072
max_used_connections=0
max_threads=65537
thread_count=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 4592 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
 
Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
mariadbd.exe!my_sigabrt_handler()[my_thr_init.c:465]
ucrtbase.dll!raise()
ucrtbase.dll!abort()
ucrtbase.dll!_get_wpgmptr()
ucrtbase.dll!_wassert()
mariadbd.exe!recv_sys_t::parse()[log0recv.cc:2127]
mariadbd.exe!recv_scan_log_recs()[log0recv.cc:2997]
mariadbd.exe!recv_group_scan_log_recs()[log0recv.cc:3080]
mariadbd.exe!recv_recovery_from_checkpoint_start()[log0recv.cc:3390]
mariadbd.exe!srv_start()[srv0start.cc:1531]
mariadbd.exe!innodb_init()[ha_innodb.cc:4058]
mariadbd.exe!ha_initialize_handlerton()[handler.cc:584]
mariadbd.exe!plugin_initialize()[sql_plugin.cc:1459]
mariadbd.exe!plugin_init()[sql_plugin.cc:1752]
mariadbd.exe!init_server_components()[mysqld.cc:4992]
mariadbd.exe!win_main()[mysqld.cc:5541]
mariadbd.exe!mysql_service()[mysqld.cc:5789]
mariadbd.exe!mysqld_main()[mysqld.cc:5984]
mariadbd.exe!main()[main.cc:26]
mariadbd.exe!__scrt_common_main_seh()[exe_common.inl:288]
 
---------SERVER LOG END-------------
mysqltest failed but provided no output
The result from queries just before the failure was:
< snip >
SET INNODB_STRICT_MODE=ON;
CREATE TABLE tdd(a INT) ENGINE=InnoDB, DATA DIRECTORY='MYSQL_TMP_DIR';
CREATE TABLE tp(a INT) ENGINE=InnoDB ROW_FORMAT=DYNAMIC PAGE_COMPRESSED=1;
CREATE TABLE ti(a INT) ENGINE=InnoDB;
FLUSH TABLES ti FOR EXPORT;
backup: ti
UNLOCK TABLES;
ALTER TABLE ti DISCARD TABLESPACE;
restore: ti .ibd and .cfg files
ALTER TABLE ti IMPORT TABLESPACE;
BEGIN;
INSERT INTO tr VALUES(1);
INSERT INTO tc VALUES(1);
INSERT INTO td VALUES(1);
INSERT INTO tz VALUES(1);
INSERT INTO tdd VALUES(1);
INSERT INTO tp VALUES(1);
INSERT INTO ti VALUES(1);
# Kill the server
# restart
 
log file: http://buildbot.askmonty.org/buildbot/builders/winx64-debug/builds/18481/steps/test/logs/stdio



 Comments   
Comment by Marko Mäkelä [ 2020-06-02 ]

MDEV-22027 could have increased the probability of this failure in 10.5. This report could also be simply duplicating MDEV-13830, which affects 10.2 already.

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