[MDEV-30100] Assertion `purge_sys.tail.trx_no <= purge_sys.rseg->last_trx_no()' - Jira

XML

Word

Printable

Type: Bug
Status: Closed (View Workflow)
Priority: Critical
Resolution: Fixed
Affects Version/s: 10.5.16, 11.2.0, 10.5, 10.6, 10.7(EOL), 10.8(EOL), 10.9(EOL), 10.10(EOL), 10.11, 11.0(EOL), 11.1(EOL), 11.2(EOL)
Fix Version/s: 10.6.16, 10.10.7, 10.11.6, 11.0.4, 11.1.3, 11.2.2
Component/s: Storage Engine - InnoDB
Labels:
- rr-profile
Environment:
centos 7.6

The process exits during mysqld execution, and an error occurs after restarting.

lead to:

InnoDB: Failing assertion: purge_sys.tail.trx_no <= purge_sys.rseg->last_trx_no()

InnoDB: We intentionally generate a memory trap.

InnoDB: Submit a detailed bug report to https://jira.mariadb.org/

InnoDB: If you get repeated assertion failures or crashes, even

InnoDB: immediately after the mysqld startup, there may be

InnoDB: corruption in the InnoDB tablespace. Please refer to

InnoDB: https://mariadb.com/kb/en/library/innodb-recovery-modes/

InnoDB: about forcing recovery.

220914 18:23:30 [ERROR] mysqld got signal 6 ;

causes

MDEV-32103 InnoDB ALTER TABLE is not crash safe

duplicates

MDEV-30261 mysqld got signal 6 ;

relates to

MDEV-29401 InnoDB history list length increased in 10.6 compared to 10.5 for the same load

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.