The Ultimate Guide to High Availability with MariaDB

Upgrading from MariaDB 10.6 to MariaDB 10.11

You are viewing an old version of this article. View the current version here.

Contents

  1. How to Upgrade
  2. Incompatible Changes Between 10.6 and 10.11
    1. Compression
    2. Options That Have Changed Default Values
    3. Options That Have Been Removed or Renamed
    4. Deprecated Options
  3. See Also

This page includes details for upgrading from MariaDB 10.6 to the subsequent long-term maintenance version, MariaDB 10.11. It is currently incomplete.

How to Upgrade

For Windows, see Upgrading MariaDB on Windows.

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

The suggested upgrade procedure is:

  1. Modify the repository configuration, so the system's package manager installs MariaDB 10.11. For example,
  2. Stop MariaDB.
  3. 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
  4. Install the new version of MariaDB.
  5. Make any desired changes to configuration options in option files, such as my.cnf. This includes removing any options that are no longer supported.
  6. Start MariaDB.
  7. Run mariadb-upgrade.
    • mariadb-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.6 and 10.11

On most servers upgrading from 10.6 should be painless. However, there are some things that have changed which could affect an upgrade:

Compression

If a non-zlib compression algorithm was used in InnoDB or Mroonga before upgrading to 10.11, those tables will be unreadable until the appropriate compression library is installed. See Compression Plugins#Upgrading.

Options That Have Changed Default Values

OptionOld defaultNew default
innodb_buffer_pool_chunk_size134217728Autosized
spider_auto_increment_mode-10
spider_bgs_first_read-12
spider_bgs_mode-10
spider_bgs_second_read-1100
spider_bka_mode-11
spider_bka_table_name_type-11
spider_buffer_size-116000
spider_bulk_size-116000
spider_bulk_update_mode-10
spider_bulk_update_size-116000
spider_casual_read-10
spider_connect_timeout-16
spider_crd_bg_mode-12
spider_crd_interval-151
spider_crd_mode-11
spider_crd_sync-10
spider_crd_type-12
spider_crd_weight-12
spider_delete_all_rows_type-11
spider_direct_dup_insert-10
spider_direct_order_limit-19223372036854775807
spider_error_read_mode-10
spider_error_write_mode-10
spider_first_read-10
spider_init_sql_alloc_size-11024
spider_internal_limit-19223372036854775807
spider_internal_offset-10
spider_internal_optimize-10
spider_internal_optimize_local-10
spider_load_crd_at_startup-11
spider_load_sts_at_startup-11
spider_low_mem_read-11
spider_max_order-132767
spider_multi_split_read-1100
spider_net_read_timeout-1600
spider_net_write_timeout-1600
spider_quick_mode-13
spider_quick_page_byte-110485760
spider_quick_page_size-11024
spider_read_only_mode-10
spider_reset_sql_alloc-11
spider_second_read-10
spider_selupd_lock_mode-11
spider_semi_split_read-12
spider_semi_split_read_limit-11
spider_semi_table_lock_connection-11
spider_semi_table_lock10

Options That Have Been Removed or Renamed

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

OptionReason
innodb_log_write_ahead_sizeOn Linux and Windows, the physical block size of the underlying storage is instead detected and used.
wsrep_replicate_myisamUse wsrep_mode instead.
wsrep_strict_ddlUse wsrep_mode instead.

Deprecated Options

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.

OptionReason
keep_files_on_createMariaDB now deletes orphan files, so this setting should never be necessary.

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.