[MDEV-30825] innodb_compression_algorithm=0 (none) increments Innodb_num_pages_page_compression_error Created: 2023-03-09  Updated: 2023-10-18  Resolved: 2023-10-18

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: 10.3.37, 10.4.28, 10.5.19, 10.6.12, 10.7, 10.8, 10.9, 10.10, 10.11, 11.0
Fix Version/s: 10.4.32, 10.5.23, 10.6.16, 10.10.7, 10.11.6, 11.0.4, 11.1.3

Type: Bug Priority: Major
Reporter: Roel Van de Paar Assignee: Daniel Black
Resolution: Fixed Votes: 0
Labels: compression, regression-10.7


 Description    

SET GLOBAL innodb_checksum_algorithm=1, innodb_compression_algorithm=0;
 
CREATE TABLE t (c INT) page_compressed=1 page_compression_level=4 ENGINE=InnoDB;
 
SHUTDOWN;

Leads to:

11.0.1 f2dc4d4c10ac36a73b5c1eb765352d3aee808d66 (Optimized)

 
2023-03-07 21:44:53 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1"
 
2023-03-07 21:44:53 0 [Warning] InnoDB: Page compression errors: 3
 
2023-03-07 21:44:53 0 [Note] InnoDB: Shutdown completed; log sequence number 58233; transaction id 19

Bug confirmed present in:
MariaDB: 10.4.29 (dbg), 10.4.29 (opt), 10.7.8 (dbg), 10.7.8 (opt), 10.8.8 (dbg), 10.8.8 (opt), 10.9.6 (dbg), 10.9.6 (opt), 10.10.4 (dbg), 10.10.4 (opt), 10.11.2 (dbg), 10.11.2 (opt), 11.0.1 (dbg), 11.0.1 (opt)

Discussed with danblack who already developed a fix.

 Comments   
Comment by Daniel Black [ 2023-03-10 ]

https://github.com/MariaDB/server/pull/2538

note two questions in PR on getting the test case cleaner/right.

Comment by Roel Van de Paar [ 2023-03-10 ]

Interestingly, with this testcase:

SET GLOBAL innodb_checksum_algorithm=1, innodb_compression_algorithm=0;
 
CREATE TABLE t (c INT) page_compressed=1 page_compression_level=4 ENGINE=InnoDB;
 
FLUSH TABLES;
 
SELECT SLEEP(2);
 
SHOW GLOBAL STATUS LIKE 'Innodb_num_pages_page_compression_error';

I can repeat the issue in 10.4 dbg/opt (Innodb_num_pages_page_compression_error console output only, no error log warning) rev cacea31687c098c0348deb1e433f4baddd817419. However, not in any other version (tested 10.5 to 10.7). And in 10.7+ we have the error log warning.
It seems there is a difference between versions (10.4, 10.5/6, 10.7+)

Comment by Roel Van de Paar [ 2023-03-10 ]

Also interesting is that using --log-bin or not may make a difference in the issue reproducing or not.

Comment by Marko Mäkelä [ 2023-03-10 ]

Thank you. Was this caused by MDEV-12026?

Comment by Roel Van de Paar [ 2023-03-11 ]

Possibly. It already existed in an early 10.9 build from 14/2/2022 (verified). Bisecting would be hard given odd timing/sporadic behaviors across earlier versions.

Comment by Daniel Black [ 2023-10-17 ]

updated PR 2538 (finally) with test case fixes.

Comment by Marko Mäkelä [ 2023-10-17 ]

OK to push after simplifying the test case.

Generated at Thu Feb 08 10:19:11 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.