Upgrading from MariaDB 10.0 to MariaDB 10.1

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. For Windows, see Upgrading MariaDB on Windows instead.
2. Set innodb_fast_shutdown to 0.
3. Shutdown MariaDB 10.0
4. Take a backup (this is the perfect time to take a backup of your databases)
5. Uninstall MariaDB 10.0
6. Install MariaDB 10.1 ^[1]
7. 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)
8. 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.

Replication

• MariaDB 10.1 introduces new, standards-compliant behavior for dealing with primary keys over nullable columns. In certain edge cases this could cause replication issues when replicating from a MariaDB 10.0 master to a MariaDB 10.1 slave using statement-based replication. See MDEV-12248.

Galera

See Upgrading Galera Cluster from MariaDB 10.0 to 10.1 for more details on Galera upgrades.

Options That Have Changed Default Values

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

Options That Have Been Removed or Renamed

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

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:

• Galera Cluster is now included by default.
• Encryption
• InnoDB/XtraDB Page Compression

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

• The features in MariaDB 10.1
• Upgrading from MariaDB 10.1 to MariaDB 10.2
• Upgrading from MariaDB 5.5 to MariaDB 10.0