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

InnoDB LZ4 and LZMA compression algorithms aren't available on Debian 9

Details

    Description

      Server version: 10.3.17-MariaDB-1:10.3.17+maria~stretch-log mariadb.org binary distribution
       
      MariaDB [(none)]> set global innodb_compression_algorithm='lz4';
      ERROR 1231 (42000): Variable 'innodb_compression_algorithm' can't be set to the value of 'lz4'
       
      MariaDB [(none)]> show global status like '%have%';
      +------------------------+-------+
      | Variable_name          | Value |
      +------------------------+-------+
      | Innodb_have_lz4        | OFF   |
      | Innodb_have_lzo        | OFF   |
      | Innodb_have_lzma       | OFF   |
      | Innodb_have_bzip2      | OFF   |
      | Innodb_have_snappy     | OFF   |
      | Innodb_have_punch_hole | ON    |
      +------------------------+-------+
       
      2019-08-05 15:20:02 0 [ERROR] InnoDB: innodb_compression_algorithm = 2 unsupported.
      InnoDB: liblz4 is not installed. 
      

      But lz4 is installed on the system and the server appears to have been compiled with it:

      # ls -l /usr/lib/x86_64-linux-gnu/liblz4.so.1
      lrwxrwxrwx 1 root root 15 Feb 17  2016 /usr/lib/x86_64-linux-gnu/liblz4.so.1 -> liblz4.so.1.7.1
      # ldd /usr/sbin/mysqld | grep lz4
      	liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1 (0x00007f4c87b9a000)
      

      Attachments

        Issue Links

          Activity

            I've check this and if you have liblz4-1 installed MariaDB 10.3 will show list like this (same goes with rest of compressions if you have library they will be enabled):

            MariaDB [(none)]> show global status like '%have%';
            +------------------------+-------+
            | Variable_name          | Value |
            +------------------------+-------+
            | Innodb_have_lz4        | ON    |
            | Innodb_have_lzo        | OFF   |
            | Innodb_have_lzma       | OFF   |
            | Innodb_have_bzip2      | OFF   |
            | Innodb_have_snappy     | OFF   |
            | Innodb_have_punch_hole | ON    |
            +------------------------+-------+
            6 rows in set (0.003 sec)
             
            MariaDB [(none)]> set global innodb_compression_algorithm='lz4';
            Query OK, 0 rows affected (0.000 sec)
            

            In MariaDB 10.3 compression libraries are not installed as preset. They are done from MariaDB 10.7 when you install correct compression plugin beides mariadb-server. As MariaDB will EOL after next release I doubt this won't be changed.

            illuusio Tuukka Pasanen added a comment - I've check this and if you have liblz4-1 installed MariaDB 10.3 will show list like this (same goes with rest of compressions if you have library they will be enabled): MariaDB [(none)]> show global status like '%have%'; +------------------------+-------+ | Variable_name | Value | +------------------------+-------+ | Innodb_have_lz4 | ON | | Innodb_have_lzo | OFF | | Innodb_have_lzma | OFF | | Innodb_have_bzip2 | OFF | | Innodb_have_snappy | OFF | | Innodb_have_punch_hole | ON | +------------------------+-------+ 6 rows in set (0.003 sec)   MariaDB [(none)]> set global innodb_compression_algorithm='lz4'; Query OK, 0 rows affected (0.000 sec) In MariaDB 10.3 compression libraries are not installed as preset. They are done from MariaDB 10.7 when you install correct compression plugin beides mariadb-server. As MariaDB will EOL after next release I doubt this won't be changed.

            illuusio, what I mainly wanted to know is whether this bug was fixed on newer Debian, for Debian’s own packages of MariaDB Server. You seem to confirm that for MariaDB’s Debian packages, it was likely fixed in MariaDB Server 10.7 (which already reached EOL). Has this been fixed in the most recent Debian’s package of MariaDB Server 10.11? (10.11 is the first long-term-support release after 10.6.)

            marko Marko Mäkelä added a comment - illuusio , what I mainly wanted to know is whether this bug was fixed on newer Debian, for Debian’s own packages of MariaDB Server. You seem to confirm that for MariaDB’s Debian packages, it was likely fixed in MariaDB Server 10.7 (which already reached EOL). Has this been fixed in the most recent Debian’s package of MariaDB Server 10.11? (10.11 is the first long-term-support release after 10.6.)

            I don't know is there anything to be done with this? marko or danblack?

            illuusio Tuukka Pasanen added a comment - I don't know is there anything to be done with this? marko or danblack ?

            illuusio, if all compression libraries are available in Debian 12 out of the box, I would close this as fixed in MariaDB 10.11 or something.

            marko Marko Mäkelä added a comment - illuusio , if all compression libraries are available in Debian 12 out of the box, I would close this as fixed in MariaDB 10.11 or something.
            illuusio Tuukka Pasanen added a comment - - edited

            As said if you install MariaDB 10.7 or 10.11 for example on any supported Debian with correct compression plugin I think this is fixed.

            illuusio Tuukka Pasanen added a comment - - edited As said if you install MariaDB 10.7 or 10.11 for example on any supported Debian with correct compression plugin I think this is fixed.

            People

              illuusio Tuukka Pasanen
              tanj Guillaume Lefranc
              Votes:
              2 Vote for this issue
              Watchers:
              8 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.