Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Percona 5.7.32-35 Crashs while Optimize Table

Description

One off our Read-Only Slaves crashed will executing an Optimize Table on an InnoDB Table. Before executing the command we set innodb_optimize_fulltext_only via "SET GLOBAL innodb_optimize_fulltext_only = ON". The optimize table was executed a few times in a row and was done after a few seconds until one run crashed.

The table contains 2 FTS Indices which seem to cause the problem.

Environment

None

AFFECTED CS IDs

CS0032627, CS0032978

Smart Checklist

Activity

Show:

Yura Sorokin February 16, 2023 at 3:49 PM

Yura Sorokin January 30, 2023 at 5:16 PM

Yura Sorokin January 30, 2023 at 5:15 PM

A stack trace from MacOS

Yura Sorokin January 30, 2023 at 5:13 PM

Here is an MTR test case fragment that helps to reproduce the problem in a single run

Jaime Sicam January 30, 2023 at 6:36 AM

Reproduced on Percona Server 8.0.30:

From MySQL console, enable innodb_optimize_fulltext_only=1 and create test table

 

Populate the test table:

Run mysqlslap:

MySQL error log:

 

 

 

 

 

 

Done

Details

Assignee

Reporter

Upstream Bug URL

https://bugs.mysql.com/bug.php?id=109467

Needs Review

Yes

Fix versions

Affects versions

Priority

Smart Checklist

Created February 1, 2021 at 2:48 PM
Updated March 19, 2025 at 8:56 AM
Resolved February 16, 2023 at 3:49 PM