[MDEV-25811] InnoDB: Unable to find a record to delete-mark Created: 2021-05-28  Updated: 2022-03-08  Resolved: 2022-03-08

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: 10.5.10
Fix Version/s: N/A

Type: Bug Priority: Critical
Reporter: Alex Assignee: Marko Mäkelä
Resolution: Cannot Reproduce Votes: 1
Labels: None
Environment:

Debian Buster


 Description    

2021-05-28 18:03:18 0 [ERROR] InnoDB: Unable to find a record to delete-mark
 
InnoDB: tuple DATA TUPLE: 5 fields;
 
 0: len 4; hex 00071513; asc     ;;
 
 1: len 1; hex 00; asc  ;;
 
 2: len 4; hex 9f4f25d4; asc  O% ;;
 
 3: len 1; hex 01; asc  ;;
 
 4: len 4; hex 024f8a89; asc  O  ;;
 
 
 
InnoDB: record PHYSICAL RECORD: n_fields 5; compact format; info bits 0
 
 0: len 4; hex 00071511; asc     ;;
 
 1: len 1; hex 01; asc  ;;
 
 2: len 4; hex a75151a3; asc  QQ ;;
 
 3: len 1; hex 02; asc  ;;
 
 4: len 4; hex 032e2727; asc  .'';;   
2021-05-28 18:03:18 0 [ERROR] InnoDB: page [page id: space=1306, page number=174738] (661 records, index id 4331).
 
2021-05-28 18:03:18 0 [ERROR] InnoDB: Submit a detailed bug report to https://jira.mariadb.org/



 Comments   
Comment by Sergei Golubchik [ 2021-06-05 ]

related to MDEV-22373?

Comment by Marko Mäkelä [ 2022-01-25 ]

The 10.5 series was affected by MDEV-25783, which had been fixed in the 10.5.11 release.

alexcool, can you repeat this with a newer version? Or if you do

SET GLOBAL innodb_change_buffering=none;

Note: This will not repair already corrupted secondary indexes. To do that, you must execute DROP INDEX and CREATE INDEX on the corrupted indexes.

Comment by Alex [ 2022-01-30 ]

Right now we are using Three servers with versions master: 10.5.11, replicas: 10.5.12, 10.5.13

We are using

innodb_change_buffering=none

as a workaround.

Is it save to use

innodb_change_buffering=all

with our versions our servers?

Comment by Marko Mäkelä [ 2022-03-08 ]

In MDEV-27734, the default was changed to innodb_change_buffering=none because users and customers have experienced corruption that we are unable to reproduce. In MDEV-27735 the parameter was deprecated, to be removed in a future release.

In MDEV-11634 you can find some benchmark results, estimating the performance impact of the change buffer. In our tests on SSD, it improved performance by at most 5%. Sometimes it reduces performance or just makes the system tablespace grow insanely (MDEV-21952, MDEV-27153).

I would not recommend using the change buffer.

If you are able to provide anything that reliably repeats this corruption, feel free to reopen this.

Generated at Thu Feb 08 09:40:35 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.