[MDEV-32146] MariaDB instance goes down due to InnoDB: Failing assertion Created: 2023-09-11  Updated: 2023-10-16  Resolved: 2023-10-16

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

Type: Bug Priority: Major
Reporter: Vladimir Endaltsev Assignee: Unassigned
Resolution: Incomplete Votes: 0
Labels: crash, innodb
Environment:

CentOS Linux release 7.9.2009, KVM guest, hostname ml0001.prod.co.dc03.hosted.exlibrisgroup.com

Attachments: File ml0001.err    

 Description   

Problematic behavior can be reproduced with insert as select written in stacktrace:

INSERT INTO kbal4.KB_AUTHORS_FT_INDEX_TEMP ( LAST_NAME_NORMALIZED,OWNER,FULL_NAME_FORMAT,FIRST_NAME_NORMALIZED,AVAILABLE_FOR,FULL_NAME_NORMALIZED,AUTHOR_ID,OBJECT_ID,AUTHOR_TYPE )
SELECT LAST_NAME_NORMALIZED,OWNER,FULL_NAME_FORMAT,FIRST_NAME_NORMALIZED,AVAILABLE_FOR,FULL_NAME_NORMALIZED,AUTHOR_ID,OBJECT_ID,AUTHOR_TYPE
FROM kbal4.KB_AUTHORS;

However table is not identified as corrupted and requires repair.

 Comments   
Comment by Marko Mäkelä [ 2023-09-11 ]

In ml0001.err, we can see the following:

mariadb-10.4.21

 
2023-09-10 09:38:40 0x7f5fc8335700  InnoDB: Assertion failure in file /home/buildbot/buildbot/build/storage/innobase/pars/pars0pars.cc line 772
 
InnoDB: Failing assertion: sym_node->table != NULL

This assertion fails in the InnoDB internal SQL parser, which is being used for updating the internal tables that are related to the FULLTEXT INDEX implementation.

Can you please check if the error would go away if you rebuild the table?

ALTER TABLE kbal4.KB_AUTHORS_FT_INDEX_TEMP FORCE;

This should rebuild the underlying FULLTEXT INDEX related tables as well.

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