Missing rows after ALGORITHM=INPLACE ALTER under same workload as PS-9092

Description

In same workload that resulted in https://perconadev.atlassian.net/browse/PS-9092, we hit an issue where after accidentally running a null ALTER with ALGORITHM=INPLACE, a row was missing. No delete was found in the binlog for the row in question.

Normal process was to do the null alter to reclaim disk space by stopping replication, running the ALTER with ALGORITHM=COPY, then restarting replication after the ALTER was complete. Inadvertently, the ALTER was run with INPLACE and replication was not stopped.

Environment

None

Attachments

1
  • 26 Aug 2024, 12:36 PM

Activity

Show:

Dmitry Lenev September 3, 2024 at 3:03 PM

Fix has been pushed to 8.0.39 and 8.4.2 release trees.

mohit.joshi August 26, 2024 at 12:35 PM

The fix has been tested and it works as expected. Attached script (which involves pstress tool) was used to test and verify the results.

Dmitry Lenev July 18, 2024 at 10:06 PM

We have submitted our tentative fix for the problem to Upstream as a contribution.

Dmitry Lenev July 16, 2024 at 1:31 PM

This issue has been reported to Upstream https://bugs.mysql.com/bug.php?id=115608

Aaditya Dubey July 10, 2024 at 7:41 AM

Hi
Thank you for the test case.
The report is verified now!

Done

Details

Security Level Help

None

Assignee

Reporter

Needs QA

Yes

Affects versions

Priority

Smart Checklist

Created March 14, 2024 at 6:35 PM
Updated November 4, 2024 at 12:33 PM
Resolved September 3, 2024 at 3:03 PM