> For the complete documentation index, see [llms.txt](https://mariadb.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mariadb.com/docs/galera-cluster/galera-management/upgrading-galera-cluster/upgrading-from-mariadb-10.11-to-mariadb-11.4-with-galera-cluster-1.md).

# Upgrading from MariaDB 11.4 to MariaDB 11.8 with Galera Cluster

[Galera Cluster](/docs/galera-cluster/readme.md) ships with the MariaDB Server. Upgrading a Galera Cluster node is very similar to upgrading a server from [MariaDB 11.4](/docs/release-notes/community-server/11.4/what-is-mariadb-114.md) to [MariaDB 11.8](/docs/release-notes/community-server/11.8/what-is-mariadb-118.md). For more information on that process as well as incompatibilities between versions, see the [Upgrade Guide](/docs/server/server-management/install-and-upgrade-mariadb/upgrading.md). 

## Performing a Rolling Upgrade

The following steps can be used to perform a rolling upgrade from MariaDB 10.11 to MariaDB 11.4 when using Galera Cluster. In a rolling upgrade, each node is upgraded individually, so the cluster is always operational. There is no downtime from the application's perspective\[cite: 5, 6, 7, 8]. 

First, before you get started: 

1. Take a look at [Upgrading from MariaDB 11.4 to MariaDB 11.8](/docs/server/server-management/install-and-upgrade-mariadb/upgrading/mariadb-community-server-upgrade-paths/upgrading-from-mariadb-11-4-to-mariadb-11-8.md) to see what has changed between the major versions. 
2. System-Versioned Tables Performance Warning: MariaDB 11.8 extends the maximal allowed value for timestamps up to `'2106-02-07 06:28:15 UTC'`. If you are using system-versioned tables, all rows and indexes must be updated to use this extended range. Upgrading to 11.8 can take a long time if you have many rows in your system-versioned tables! If you are not using system-versioned tables, the upgrade should execute rapidly.
3. Check whether any system variables or options have been changed or removed. For example, the `alter_algorithm` system variable has been deprecated and is ignored since [MariaDB 11.5](/docs/release-notes/community-server/old-releases/11.5/what-is-mariadb-115.md). Make sure that your server's configuration is compatible with the new MariaDB version before upgrading.
4. Character Set Default Shift: The default character set changes from `latin1` to `utf8mb4`. Ensure your database parameters align or explicitly define your previous collation options in your configuration files if you maintain legacy replication branches.
5. Check whether replication has changed in the new MariaDB version in any way that could cause issues while the cluster contains upgraded and non-upgraded nodes. 
6. Check whether any new features have been added to the new MariaDB version. If a new feature (such as the new [VECTOR](/docs/server/reference/sql-structure/vectors.md) data type or parsec authentication plugin) cannot be replicated to the old MariaDB version, then do not use that feature until all cluster nodes have been upgraded.
7. Next, make sure that the Galera version numbers are compatible. Both MariaDB 11.4 and 11.8 releases ship with modern releases of Galera 4 (wsrep API 26). For the purposes of a rolling upgrade, ensure your versions align across these ecosystem baselines.
8. See [What is MariaDB Galera Cluster](/docs/galera-cluster/readme/mariadb-galera-cluster-guide.md)?: Galera wsrep provider Versions for information on which MariaDB releases use which Galera wsrep provider versions. 
9. You want to have a large enough gcache to avoid a State Snapshot Transfer (SST) during the rolling upgrade. The gcache size can be configured by setting gcache.size. For example: [wsrep\_provider\_options](/docs/galera-cluster/reference/wsrep-variable-details/wsrep_provider_options.md)="gcache.size=2G". 

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. 

Then, for each node, perform the following steps:

{% stepper %}
{% step %}
Modify the repository configuration, so the system's package manager installs [MariaDB 11.8](/docs/release-notes/community-server/11.8/what-is-mariadb-118.md).

{% tabs %}
{% tab title="Debian, Ubuntu, ..." %}
see [Updating the MariaDB APT repository to a New Major Release](/docs/server/server-management/install-and-upgrade-mariadb/installing-mariadb/binary-packages/installing-mariadb-deb-files.md) for more information.
{% endtab %}

{% tab title="RHEL, CentOS, Fedora, ..." %}
see [Updating the MariaDB YUM repository to a New Major Release](/docs/server/server-management/install-and-upgrade-mariadb/installing-mariadb/binary-packages/rpm/yum.md) for more information.
{% endtab %}

{% tab title="SLES, OpenSUSE, ..." %}
see [Updating the MariaDB ZYpp repository to a New Major Release](/docs/server/server-management/install-and-upgrade-mariadb/installing-mariadb/binary-packages/rpm/installing-mariadb-with-zypper.md) for more information.ser
{% endtab %}
{% endtabs %}
{% endstep %}

{% step %}
If you use a load balancing proxy such as [MaxScale](/docs/maxscale/maxscale-quickstart-guides.md) or HAProxy, make sure to drain the server from the pool so it does not receive any new connections.
{% endstep %}

{% step %}
[Stop MariaDB](/docs/server/server-management/starting-and-stopping-mariadb.md).
{% endstep %}

{% step %}
Uninstall the old version of MariaDB and the Galera wsrep provider.

{% tabs %}
{% tab title="Debian, Ubuntu, ..." %}
{% code overflow="wrap" expandable="true" %}

```bash
sudo apt-get remove mariadb-server galera
```

{% endcode %}
{% endtab %}

{% tab title="RHEL, CentOS, Fedora, ..." %}
{% code overflow="wrap" expandable="true" %}

```bash
sudo yum remove MariaDB-server galera
```

{% endcode %}
{% endtab %}

{% tab title="SLES, OpenSUSE, ..." %}
{% code overflow="wrap" expandable="true" %}

```bash
sudo zypper remove MariaDB-server galera
```

{% endcode %}
{% endtab %}
{% endtabs %}
{% endstep %}

{% step %}
Install the new version of MariaDB and the Galera wsrep provider\[cite: 5, 6, 7, 8].

{% tabs %}
{% tab title="Debian, Ubuntu, ..." %}
see Installing MariaDB Packages with APT for more information.
{% endtab %}

{% tab title="RHEL, CentOS, Fedora, ..." %}
see [Installing MariaDB Packages with YUM](/docs/server/server-management/install-and-upgrade-mariadb/installing-mariadb/binary-packages/rpm/yum.md) for more information\[cite: 5, 6, 7, 8].
{% endtab %}

{% tab title="SLES, OpenSUSE, ..." %}
see [Installing MariaDB Packages with ZYpp](/docs/server/server-management/install-and-upgrade-mariadb/installing-mariadb/binary-packages/rpm/installing-mariadb-with-zypper.md) for more information.
{% endtab %}
{% endtabs %}
{% endstep %}

{% step %}
Make any desired changes to configuration [options](/docs/server/server-management/install-and-upgrade-mariadb/configuring-mariadb/configuring-mariadb-with-option-files.md) in option files, such as `my.cnf`. This includes removing any system variables or options that are no longer supported.
{% endstep %}

{% step %}
On Linux distributions that use `systemd` you may need to increase the service startup timeout as the default timeout of ninety seconds may not be sufficient(especially if system-versioned tables trigger structural row scans). See [Systemd: Configuring the Systemd Service Timeout](/docs/server/server-management/starting-and-stopping-mariadb/systemd.md) for more information.
{% endstep %}

{% step %}
[Start MariaDB](/docs/server/server-management/starting-and-stopping-mariadb.md).
{% endstep %}

{% step %}
Run [mysql\_upgrade](/docs/server/clients-and-utilities/legacy-clients-and-utilities/mysql_upgrade.md) (or [mariadb-upgrade](/docs/server/clients-and-utilities/deployment-tools/mariadb-upgrade.md)) with the `--skip-write-binlog` option. `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
   {% endstep %}
   {% endstepper %}

When this process is done for one node, move onto the next node\[cite: 5, 6, 7, 8].

{% hint style="warning" %}
When upgrading the Galera wsrep provider, sometimes the Galera protocol version can change. The Galera wsrep provider should not start using the new protocol version until all cluster nodes have been upgraded to the new version, so this is not generally an issue during a rolling upgrade. However, this can cause issues if you restart a non-upgraded node in a cluster where the rest of the nodes have been upgraded.
{% endhint %}

{% @marketo/form formId="4316" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://mariadb.com/docs/galera-cluster/galera-management/upgrading-galera-cluster/upgrading-from-mariadb-10.11-to-mariadb-11.4-with-galera-cluster-1.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.