Join the community today
Register Now

MariaDB Warning about innodb_file_format - Deprecated/Removed

Discussion in 'Nginx, PHP-FPM & MariaDB MySQL' started by Revenge, Mar 15, 2018.

  1. Revenge

    Revenge Active Member

    469
    93
    28
    Feb 21, 2016
    Portugal
    Ratings:
    +354
    Local Time:
    2:02 PM
    1.9.x
    10.1.x
    innodb_file_format was deprecated in MariaDB 10.2 and removed in MariaDB 10.3.

    Since MariaDB 10.2.2 the default is Barracuda, so there is no need to set this variable.

    It's better to remove it now from the conf file, because when the time comes for us to upgrade to MariaDB 10.3, if its still there, MariaDB won't start

    PS: Same thing for innodb_large_prefix.


     
    Last edited: Mar 15, 2018
  2. eva2000

    eva2000 Administrator Staff Member

    55,247
    12,253
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +18,833
    Local Time:
    11:02 PM
    Nginx 1.27.x
    MariaDB 10.x/11.4+
    thanks for heads up though Centmin Mod users don't have to worry as it's been the default on initial installs in 123.09beta01 :D
    Code (Text):
    mysqladmin var | egrep 'innodb_file_format |large_prefix' | tr -s ' '
    | innodb_file_format | Barracuda |
    | innodb_large_prefix | ON |
     
  3. Revenge

    Revenge Active Member

    469
    93
    28
    Feb 21, 2016
    Portugal
    Ratings:
    +354
    Local Time:
    2:02 PM
    1.9.x
    10.1.x
    But centminmod sets the value in my.cnf correct?
     
  4. eva2000

    eva2000 Administrator Staff Member

    55,247
    12,253
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +18,833
    Local Time:
    11:02 PM
    Nginx 1.27.x
    MariaDB 10.x/11.4+
    Yup Centmin Mod at initial install time automatically uses those values as default :)
     
  5. Revenge

    Revenge Active Member

    469
    93
    28
    Feb 21, 2016
    Portugal
    Ratings:
    +354
    Local Time:
    2:02 PM
    1.9.x
    10.1.x
    MariaDB since 10.2.2 have those values by default, so centminmod does not need to set them at initial install times.
    The issue here is that if someone upgrades to MariaDB 10.3, those variables are no longer valid, so if they are set in my.cnf, MariaDB won't start.
     
  6. wmtech

    wmtech Active Member

    175
    44
    28
    Jul 22, 2017
    Ratings:
    +132
    Local Time:
    3:02 PM
    I am sure this will be handled by the upgrade script once 10.3 is available and upgrade command will be open in centminmod. :)
     
  7. eva2000

    eva2000 Administrator Staff Member

    55,247
    12,253
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +18,833
    Local Time:
    11:02 PM
    Nginx 1.27.x
    MariaDB 10.x/11.4+
    Centmin Mod MariaDB 10.x to 10.2 and 10.3 upgrade routines will always set those custom + optimal values by default so no worries there as optimal custom settings are never lost between MariaDB major branch upgrades via centmin.sh menu option 11 submenu options :)

    Code (Text):
    --------------------------------------------------------
         Centmin Mod Menu 123.09beta01 centminmod.com     
    --------------------------------------------------------
    1).  Centmin Install
    2).  Add Nginx vhost domain
    3).  NSD setup domain name DNS
    4).  Nginx Upgrade / Downgrade
    5).  PHP Upgrade / Downgrade
    6).  XCache Re-install
    7).  APC Cache Re-install
    8).  XCache Install
    9).  APC Cache Install
    10). Memcached Server Re-install
    11). MariaDB MySQL Upgrade & Management
    12). Zend OpCache Install/Re-install
    13). Install/Reinstall Redis PHP Extension
    14). SELinux disable
    15). Install/Reinstall ImagicK PHP Extension
    16). Change SSHD Port Number
    17). Multi-thread compression: pigz,pbzip2,lbzip2...
    18). Suhosin PHP Extension install
    19). Install FFMPEG and FFMPEG PHP Extension
    20). NSD Install/Re-Install
    21). Update - Nginx + PHP-FPM + Siege
    22). Add Wordpress Nginx vhost + Cache Plugin
    23). Update Centmin Mod Code Base
    24). Exit
    --------------------------------------------------------
    Enter option [ 1 - 24 ] 11
    --------------------------------------------------------
    

    Code (Text):
    --------------------------------------------------------
         MariaDB MySQL Upgrade & Management Sub-Menu       
    --------------------------------------------------------
    0). Regenerate New MySQL Root User Password (local server)
    1). MariaDB 5.2.x Branch Upgrade Only
    2). MariaDB 5.2.x to MariaDB 5.5 YUM upgrade
    3). MariaDB 5.5 to MariaDB 10.x YUM upgrade
    4). MariaDB 5.5 to MariaDB 10.1.x YUM upgrade
    5). MariaDB 10.x to MariaDB 10.1.x YUM upgrade
    6). MariaDB 10.1.x to MariaDB 10.2.x YUM upgrade
    7). Back to Main menu
    --------------------------------------------------------
    Enter option [ 0 - 7 ] 
    
     
  8. eva2000

    eva2000 Administrator Staff Member

    55,247
    12,253
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +18,833
    Local Time:
    11:02 PM
    Nginx 1.27.x
    MariaDB 10.x/11.4+
    oh re-read that and now i see what you mean their deprecated values - yeah when i do write MariaDB 10.3 upgrade submenu option, the routines will remove them automatically. When I test submenu MariaDB submenu upgrade routines between major branches I always check MariaDB error logs for deprecated messages and errors so upgrade routines will always take care of any errors I find in the logs :)