The Ultimate Guide to High Availability with MariaDB

Upgrading from MariaDB 10.0 to MariaDB 10.1

Contents

  1. What You Need to Know
    1. How to Upgrade
    2. Incompatible Changes Between 10.0 and 10.1
      1. Storage Engines
      2. Replication
      3. Options That Have Changed Default Values
      4. Options That Have Been Removed or Renamed
      5. Other Issues
    3. Major New Features To Consider
  2. Notes
  3. See Also

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

For Windows, see Upgrading MariaDB on Windows instead.

For MariaDB Galera Cluster, see Upgrading from MariaDB Galera Cluster 10.0 to MariaDB 10.1 with Galera Cluster instead.

Before you upgrade, it would be best to take a backup of your database. This is always a good idea to do before an upgrade. We would recommend Percona XtraBackup.

The suggested upgrade procedure is:

  1. Modify the repository configuration, so the system's package manager installs MariaDB 10.1. For example,
  2. Set innodb_fast_shutdown to 0. It can be changed dynamically with SET GLOBAL. For example:
    SET GLOBAL innodb_fast_shutdown=0;
  3. Stop MariaDB.
  4. Uninstall the old version of MariaDB.
    • On Debian, Ubuntu, and other similar Linux distributions, execute the following:
      sudo apt-get remove mariadb-server
    • On RHEL, CentOS, Fedora, and other similar Linux distributions, execute the following:
      sudo yum remove MariaDB-server
    • On SLES, OpenSUSE, and other similar Linux distributions, execute the following:
      sudo zypper remove MariaDB-server
  5. Install the new version of MariaDB.
  6. Make any desired changes to configuration options in option files, such as my.cnf. This includes removing any options that are no longer supported.
  7. Start MariaDB.
  8. Run mysql_upgrade.
    • mysql_upgrade does two things:
      1. Ensures that the system tables in the mysql database are fully compatible with the new version.
      2. Does a very quick check of all tables and marks them as compatible with the new version of MariaDB .

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.

Replication

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

Major New Features To Consider

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

Notes

    See Also

    Comments

    Comments loading...
    Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.