Upgrading from MariaDB 5.5 to MariaDB 10.0

What You Need to Know

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

How to Upgrade

For Windows, see Upgrading MariaDB on Windows 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.0. 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 5.5 and 10.0

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

Options That Have Changed Default Values

Most of the following options have increased a bit in value to give better performance. They should not use much additional memory, but some of them a do use a bit more disk space.

OptionOld default valueNew default value
innodb-buffer-pool-instances18 (except on 32-bit Windows)
innodb-open-files300400 [2]
optimizer-switch...Added extended_keys=on, exists_to_in=on

Options That Have Been Removed or Renamed

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

engine-condition-pushdownReplaced with set optimizer_switch='engine_condition_pushdown=on'
innodb-adaptive-flushing-methodRemoved by XtraDB
innodb-autoextend-incrementRemoved by XtraDB
innodb-blocking-buffer-pool-restoreRemoved by XtraDB
innodb-buffer-pool-pagesRemoved by XtraDB
innodb-buffer-pool-pages-blobRemoved by XtraDB
innodb-buffer-pool-pages-indexRemoved by XtraDB
innodb-buffer-pool-restore-at-startupRemoved by XtraDB
innodb-buffer-pool-shm-checksumRemoved by XtraDB
innodb-buffer-pool-shm-keyRemoved by XtraDB
innodb-checkpoint-age-targetRemoved by XtraDB
innodb-dict-size-limitRemoved by XtraDB
innodb-doublewrite-fileRemoved by XtraDB
innodb-fast-checksumRenamed to innodb-checksum-algorithm
innodb-flush-neighbor-pagesRenamed to innodb-flush-neighbors
innodb-ibuf-accel-rateRemoved by XtraDB
innodb-ibuf-active-contractRemoved by XtraDB
innodb-ibuf-max-sizeRemoved by XtraDB
innodb-import-table-from-xtrabackupRemoved by XtraDB
innodb-index-statsRemoved by XtraDB
innodb-lazy-drop-tableRemoved by XtraDB
innodb-merge-sort-block-sizeRemoved by XtraDB
innodb-persistent-stats-root-pageRemoved by XtraDB
innodb-read-aheadRemoved by XtraDB
innodb-recovery-statsRemoved by XtraDB
innodb-recovery-update-relay-logRemoved by XtraDB
innodb-stats-auto-updateRenamed to innodb-stats-auto-recalc
innodb-stats-update-need-lockRemoved by XtraDB
innodb-sys-statsRemoved by XtraDB
innodb-table-statsRemoved by XtraDB
innodb-thread-concurrency-timer-basedRemoved by XtraDB
innodb-use-sys-stats-tableRemoved by XtraDB
xtradb-admin-commandRemoved by XtraDB

Reserved Words

New reserved word: RETURNING. This can no longer be used as an identifier without being quoted.


The SET OPTION syntax is deprecated in MariaDB 10.0. Use SET instead.

New Major Features To Consider

You should consider using the following new major features in MariaDB 10.0:

For Master / Slave Setups


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



  1. The innodb-open-files variable defaults to the value of table-open-cache (400 is the default) if it is set to any value less than 10 so long as innodb-file-per-table is set to 1 or TRUE (the default). If innodb_file_per_table is set to 0 or FALSE and innodb-open-files is set to a value less than 10, the default is 300

See Also


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.