This page includes details for upgrading from MariaDB 11.0 to MariaDB 11.1. Note that MariaDB 11.0 and MariaDB 11.1 are both short-term releases, only maintained for one year.
For Windows, see Upgrading MariaDB on Windows.
For MariaDB Galera Cluster, see Upgrading from MariaDB 10.6 to MariaDB 10.7 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 mariadb-backup.
The suggested upgrade procedure is:
Modify the repository configuration, so the system's package manager installs MariaDB 11.1. For example,
On Debian, Ubuntu, and other similar Linux distributions, see Updating the MariaDB APT repository to a New Major Release for more information.
On RHEL, CentOS, Fedora, and other similar Linux distributions, see Updating the MariaDB YUM repository to a New Major Release for more information.
On SLES, OpenSUSE, and other similar Linux distributions, see Updating the MariaDB ZYpp repository to a New Major Release for more information.
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
Install the new version of MariaDB.
On Debian, Ubuntu, and other similar Linux distributions, see Installing MariaDB Packages with APT for more information.
On RHEL, CentOS, Fedora, and other similar Linux distributions, see Installing MariaDB Packages with YUM for more information.
On SLES, OpenSUSE, and other similar Linux distributions, see Installing MariaDB Packages with ZYpp for more information.
Make any desired changes to configuration options in option files, such as my.cnf. This includes removing any options that are no longer supported.
Run mariadb-upgrade.
mariadb-upgrade does two things:
Ensures that the system tables in the mysql 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 .
On most servers upgrading from 10.11 should be painless. However, there are some things that have changed which could affect an upgrade:
The following options should be removed or renamed if you use them in your option files:
Defragmenting InnoDB Tablespaces in this manner no longer supported.
Defragmenting InnoDB Tablespaces in this manner no longer supported.
Defragmenting InnoDB Tablespaces in this manner no longer supported.
Defragmenting InnoDB Tablespaces in this manner no longer supported.
Defragmenting InnoDB Tablespaces in this manner no longer supported.
Defragmenting InnoDB Tablespaces in this manner no longer supported.
The following options have been deprecated. They have not yet been removed, but will be in a future version, and should ideally no longer be used.
The motivation for introducing this in MySQL seems to have been to avoid stalls due to freeing undo log pages or truncating undo log tablespaces. In MariaDB, innodb_undo_log_truncate=ON should be a much lighter operation because it will not involve any log checkpoint, hence this is deprecated and ignored
Replaced with transaction_isolation to align the option and system variable.
Replaced with transaction_read_only to align the option and system variable.
This page is licensed: CC BY-SA / Gnu FDL