What you need to know

There are no changes in table or index formats between MariaDB 10.0 and MariaDB 10.1, so on most servers the upgrade should be painless.

How to upgrade

The suggested upgrade procedure is:

  1. Shutdown MariaDB 10.0
  2. Take a backup (this is the perfect time to take a backup of your databases)
  3. Uninstall MariaDB 10.0
  4. Install MariaDB 10.1 [1]
  5. Run mysql_upgrade
    • Ubuntu and Debian packages do this automatically when they are installed; Red Hat, CentOS, and Fedora packages do not
    • mysql_upgrade does two things:
      1. Upgrades the permission tables in the mysql database with some new fields
      2. Does a very quick check of all tables and marks them as compatible with MariaDB 10.1
    • In most cases this should be a fast operation (depending of course on the number of tables)
  6. Add new options to my.cnf to enable features
    • If you change my.cnf then you need to restart mysqld

Incompatible changes between 10.0 and 10.1

As mentioned previously, on most servers upgrading from 10.0 should be painless. However, there are some things that have changed which could affect an upgrade:

Storage engines

  • The ARCHIVE storage engine is no longer enabled by default, and the plugin needs to be specifically enabled.
  • The BLACKHOLE storage engine is no longer enabled by default, and the plugin needs to be specifically enabled.

Options that have changed default values

Most of the following options have increased in value to give better performance.

OptionOld default valueNew default value
innodb_log_compressed_pagesONOFF
join_buffer_size128K256K
max_allowed_packet1M4M
query_alloc_block_size819216384
query_cache_size01M
query_cache_typeONOFF
sync_master_info010000
sync_relay_log010000
sync_relay_log_info010000
query_prealloc_size819224576
secure_authOFFON
sql_log_binNo longer affects replication of events in a Galera cluster.
sql_modeemptyNO_AUTO_CREATE_USER, NO_ENGINE_SUBSTITUTION
table_open_cache4002000
thread_pool_max_threads5001000

Options that have been removed or renamed

The following options should be removed or renamed if you use them in your config files:

OptionReason
rpl_recovery_rankUnused in 10.0

Other issues

Note that explicit or implicit casts from MAX(string) to INT, DOUBLE or DECIMAL now produce warnings (MDEV-8852).

New major features you should consider

You might consider using the following major new features in MariaDB 10.1:

Notes

  1. If using a MariaDB apt or yum repository, it is often enough to replace instances of '10.0' with '10.1' and then run an update/upgrade. For example, in Ubuntu/Debian update the MariaDB sources.list entry from something that looks similar to this:
    deb http://ftp.osuosl.org/pub/mariadb/repo/10.0/ubuntu trusty main
    
    To something like this:
    deb http://ftp.osuosl.org/pub/mariadb/repo/10.1/ubuntu trusty main
    
    And then run
    apt-get update && apt-get upgrade
    
    And in Red Hat, CentOS, and Fedora, change the baseurl line from something that looks like this:
    baseurl = http://yum.mariadb.org/10.0/centos6-amd64
    
    To something that looks like this:
    baseurl = http://yum.mariadb.org/10.1/centos6-amd64
    
    And then run
    yum update
    

See also

Comments

Comments loading...
Loading