Upgrading from MariaDB 10.0 to MariaDB 10.1 - Source

Revision: 120101
User: Ian Gilfillan
Date: 2020-05-19 10:49

<<toc>>
== 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

<<style class="bluebox">>
For Windows, see [[upgrading-mariadb-on-windows|Upgrading MariaDB on Windows]] instead.
<</style>>

<<style class="bluebox">>
For MariaDB Galera Cluster, see [[upgrading-galera-cluster-upgrading-from-mariadb-galera-cluster-100-to-maria|Upgrading from MariaDB Galera Cluster 10.0 to MariaDB 10.1 with Galera Cluster]] instead.
<</style>>

<<include slug="backup-xtrabackup">>

The suggested upgrade procedure is:

# Modify the repository configuration, so the system's package manager installs MariaDB 10.1. For example,
** On Debian, Ubuntu, and other similar Linux distributions, see [[installing-mariadb-deb-files/#updating-the-mariadb-apt-repository-to-a-new-major-release|Updating the MariaDB APT repository to a New Major Release]] for more information.
** On RHEL, CentOS, Fedora, and other similar Linux distributions, see [[yum/#updating-the-mariadb-yum-repository-to-a-new-major-release|Updating the MariaDB YUM repository to a New Major Release]] for more information.
** On SLES, OpenSUSE, and other similar Linux distributions, see [[installing-mariadb-with-zypper/#updating-the-mariadb-zypp-repository-to-a-new-major-release|Updating the MariaDB ZYpp repository to a New Major Release]] for more information.
# Set ##[[xtradbinnodb-server-system-variables#innodb_fast_shutdown|innodb_fast_shutdown]]## to ##0##. It can be changed dynamically with ##[[set/#global-session|SET GLOBAL]]##. For example: \\
<<code>>SET GLOBAL innodb_fast_shutdown=0;<</code>>
# [[starting-and-stopping-mariadb-automatically|Stop MariaDB]].
# Uninstall the old version of MariaDB.
** On Debian, Ubuntu, and other similar Linux distributions, execute the following: \\
<<code>>sudo apt-get remove mariadb-server<</code>>
** On RHEL, CentOS, Fedora, and other similar Linux distributions, execute the following: \\
<<code>>sudo yum remove MariaDB-server<</code>>
** On SLES, OpenSUSE, and other similar Linux distributions, execute the following: \\
<<code>>sudo zypper remove MariaDB-server<</code>>
# Install the new version of MariaDB.
** On Debian, Ubuntu, and other similar Linux distributions, see [[installing-mariadb-deb-files/#installing-mariadb-packages-with-apt|Installing MariaDB Packages with APT]] for more information.
** On RHEL, CentOS, Fedora, and other similar Linux distributions, see [[yum/#installing-mariadb-packages-with-yum|Installing MariaDB Packages with YUM]] for more information.
** On SLES, OpenSUSE, and other similar Linux distributions, see [[installing-mariadb-with-zypper/#installing-mariadb-packages-with-zypp|Installing MariaDB Packages with ZYpp]] for more information.
# Make any desired changes to configuration options in [[configuring-mariadb-with-option-files|option files]], such as ##my.cnf##. This includes removing any options that are no longer supported.
# [[starting-and-stopping-mariadb-automatically|Start MariaDB]].
# Run ##[[mysql_upgrade]]##.
** ##mysql_upgrade## does two things:
### Ensures that the system tables in the ##[[the-mysql-database-tables|mysq]]l## database are fully compatible with the new version.
### 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|ARCHIVE]] storage engine is no longer enabled by default, and the plugin needs to be specifically enabled.
* The [[blackhole|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-with-nullable-columns|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 [[binary-log-formats#statement-based|statement-based replication]]. See MDEV-12248.

==== 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|Galera Cluster]] is now included by default.
* [[data-at-rest-encryption|Encryption]]
* [[compression|InnoDB/XtraDB Page Compression]]

== Notes
<<references>>

== See Also
* [[what-is-mariadb-101|The features in MariaDB 10.1]]
* [[upgrading-galera-cluster-upgrading-from-mariadb-galera-cluster-100-to-maria|Upgrading from MariaDB Galera Cluster 10.0 to MariaDB 10.1 with Galera Cluster]]
* [[upgrading-from-mariadb-101-to-mariadb-102|Upgrading from MariaDB 10.1 to MariaDB 10.2]]
* [[upgrading-from-mariadb-55-to-mariadb-100|Upgrading from MariaDB 5.5 to MariaDB 10.0]]

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.

Upgrading from MariaDB 10.0 to MariaDB 10.1 - Source

Products

Services

Pricing

Resources

About Us

Download MariaDB