Bug #107919 InnoDB: insufficient history for index 0
Submitted: 20 Jul 2022 7:23 Modified: 27 Jul 2022 9:16
Reporter: Hendrik Woltersdorf Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:8.0.29 OS:Any
Assigned to: CPU Architecture:Any

[20 Jul 2022 7:23] Hendrik Woltersdorf
Description:
During heavy select/insert/update/delete activity on a table we get spurious errors like this:
InnoDB: insufficient history for index 0;Table definition has changed, please retry transaction

The table definition did not change in years, no "truncate table", server and application restarted before.

How to repeat:
Do insert/update/delete/select in parallel on one table.
[20 Jul 2022 7:24] Hendrik Woltersdorf
server log and config file

Attachment: dit_basta2_log.zip (application/x-zip-compressed, text), 818.84 KiB.

[20 Jul 2022 7:24] Hendrik Woltersdorf
application log snippet

Attachment: app_log.txt (text/plain), 2.55 KiB.

[20 Jul 2022 12:18] MySQL Verification Team
Hi Mr. Woltersdorf,

Thank you for your bug report.

We have inspected all the files that you have uploaded, but not in any of them is there a fully repeatable test case. What we require is a test case written in pure SQL, where you can also specify which statements are executed in which connection, if necessary.

Hence, not enough information was provided for us to be able to handle this bug. Please re-read the instructions at http://bugs.mysql.com/how-to-report.php 

If you can provide more information, feel free to add it to this bug and change the status back to 'Open'.  

Thank you for your interest in MySQL.
[27 Jul 2022 9:16] Hendrik Woltersdorf
Just for the records: 
This happens (sometimes) when one client issues "optimize table <tablename>" and another client selects from <tablename>.
[27 Jul 2022 12:52] MySQL Verification Team
Hi,

It does not help, only fully repeatable test case as a set of SQL statements is acceptable in order to process this report.