Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-30825

innodb_compression_algorithm=0 (none) increments Innodb_num_pages_page_compression_error

Details

    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.

      Attachments

        Activity

          Ascending order - Click to sort in descending order
          danblack Daniel Black added a comment -

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

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

          danblack Daniel Black added a comment - https://github.com/MariaDB/server/pull/2538 note two questions in PR on getting the test case cleaner/right.
          Roel Roel Van de Paar added a comment - - edited

          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+)

          Roel Roel Van de Paar added a comment - - edited 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+)
          Roel Roel Van de Paar added a comment -

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

          Roel Roel Van de Paar added a comment - Also interesting is that using --log-bin or not may make a difference in the issue reproducing or not.
          marko Marko Mäkelä added a comment -

          Thank you. Was this caused by MDEV-12026?

          marko Marko Mäkelä added a comment - Thank you. Was this caused by MDEV-12026 ?
          Roel Roel Van de Paar added a comment -

          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.

          Roel Roel Van de Paar added a comment - 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.
          danblack Daniel Black added a comment -

          updated PR 2538 (finally) with test case fixes.

          danblack Daniel Black added a comment - updated PR 2538 (finally) with test case fixes.
          marko Marko Mäkelä added a comment -

          OK to push after simplifying the test case.

          marko Marko Mäkelä added a comment - OK to push after simplifying the test case.

          People

            danblack Daniel Black
            Roel Roel Van de Paar
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.