[InnoDB] Assertion failure: ut0ut.cc:553 thread 140235111884544【筆記】

APPLIES TO:

MySQL Server - Version 8.0 and later
Information in this document applies to any platform.

SYMPTOMS

On : 8.0 version, Server Crash

 
ERROR
-----------------------

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Have a high load of transactions on the server
2. The page cleaner gets overloaded
3. At least one innodb page gets truncated from the undo log pages

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot trust the server under load without corruption.

CAUSE

A transaction was still active on the table mentioned, however, may not have been required for some time after, or simply the data was on a different page to when the truncation occurred.
Once the truncated page was attempted to be accessed, it was recognised as corrupted and the messages shown in the error log and then the final assertion to avoid any further corruption.
There were large data reads and purging based on end-of-month processes.

Corruption shows up in the mysqld error log like:

The ut0ut line shows that an assertion failure was thrown simply because it was unable to read all the required data from the page of the tablespace.
Multiple times in the log there are the following lines relating to truncating UNDO tablespace files.
This only happens in relation to the trx0trx.cc code which is for handling transactions.

This is explained in the following bug:
Bug.33162828: INNODB: Assertion failure: ut0ut.cc:552
 

SOLUTION

To implement the solution, please execute the following steps:

1. Download and review the release notes for the 8.0.27 version or higher.

2. Ensure that you have taken a backup of your system before upgrading.

3. Apply the upgrade in a test environment, if possible.

4. Retest the issue.

5. Migrate the solution as appropriate to other environments.