Should I upgrade to MariaDB 10.11 to 11.4 LTS Upgrade Planning now?
Decide whether to standardize new workloads on MariaDB 11.4 LTS now or hold on 10.11 longer while extension and replication compatibility settles.
Blockers
- MariaDB 11.4 removes several deprecated items, including the InnoDB Change Buffer and older deprecated variables.
- 11.4.10 ships Galera 26.4.25 and the higher GCS protocol version prevents downgrades of individual nodes after the whole cluster has been updated.
- package/mariadb-11-4 incompatible with package/mysql
- The cited Galera downgrade limitation is specifically called out for MariaDB 11.4.10, which ships Galera 26.4.25.
- package/mariadb-10-11 — EOL 2028-02
- package/mariadb-11-4 — EOL 2029-05
Who this is for
- enterprise
- low-ops
- cost-sensitive
Candidates
Standardize new workloads on MariaDB 11.4 LTS now
As of 2026-04-05, the latest MariaDB 11.4 community release is 11.4.10, released on 2026-02-04, and MariaDB documents 11.4 as the current long-term series maintained until May 2029. MariaDB 11.4 includes changes from the 11.0, 11.1, 11.2, and 11.3 lines, so moving now avoids another major-series jump later just to catch up. MariaDB also documents that 11.4 removes several deprecated items, including the InnoDB Change Buffer and older deprecated variables, so it is the line to validate against if you want a forward baseline. Pricing does not favor waiting: MariaDB lists Community Server as always free and open source, while Enterprise subscriptions are quote-based rather than publicly priced.
When to choose
Use this when you want the current MariaDB LTS baseline for new deployments and can run a focused compatibility test pass against plugins, Galera, backup tooling, and replication behavior. It is the cleaner choice if you may want MariaDB plc's current enterprise subscription path, because as of 2026-04-05 the MariaDB Engineering Policy lists 11.4 as a supported Enterprise Server series while 10.11 is not listed there.
Tradeoffs
You get the longest current community maintenance window and align new work with the current LTS branch, but you must absorb 11.x-era removals and behavior changes now instead of later.
Cautions
Do not treat this as a patch upgrade. MariaDB's upgrade docs require a standard major-version upgrade flow with backup first, package repo changes, and post-upgrade validation. If you use Galera, MariaDB 11.4.10 ships Galera 26.4.25 and notes that the higher GCS protocol version prevents downgrades of individual nodes after the whole cluster has been updated. If MySQL interoperability matters, MariaDB documents GTID incompatibility with MySQL and notes that extra collation aliases to ease MySQL-to-MariaDB replication only arrived in 11.4.5.
Sources
- mariadb.com/docs/release-notes/community-server/11.4/what-is-mariadb-114
- mariadb.com/docs/release-notes/community-server/11.4/11.4.10
- mariadb.com/docs/server/server-management/install-and-upgrade-mariadb/upgrading/mariadb-community-server-upgrade-paths/upgrading-from-mariadb-10-11-to-mariadb-11-4
- mariadb.com/pricing
Hold new workloads on MariaDB 10.11 longer and qualify 11.4 separately
As of 2026-04-05, the latest MariaDB 10.11 community release is 10.11.16, released on 2026-02-04, and MariaDB documents 10.11 as a long-term maintenance series maintained until February 2028. That means 10.11 still has an active support runway for self-managed community users, even though it is shorter than 11.4's May 2029 window. Staying on 10.11 avoids taking on the 11.x removals and major-series upgrade work for new workloads right now. Pricing is effectively unchanged for community use, because MariaDB lists Community Server as always free and open source.
When to choose
Use this when your priority is minimizing near-term operational change and your workloads depend on less-common engines, Galera behavior, or compatibility-sensitive integrations that you have not yet certified on 11.4. It is the more conservative choice for community-only estates that can accept a shorter maintenance runway and a deferred migration project.
Tradeoffs
You reduce immediate migration risk, but you also shorten the time before the next required standardization move and keep new systems on an older LTS line.
Cautions
This is weaker if you want MariaDB plc enterprise subscription alignment, because as of 2026-04-05 the published Enterprise Server support table lists 10.6 and 11.4, not 10.11. MariaDB 10.11 is still receiving fixes, but deferring does not remove later cluster and replication work; for example, when you eventually move to 11.4.10 with Galera, MariaDB documents the GCS protocol bump that blocks per-node downgrades after a full cluster update. Treat this as a time-buying option, not a final standardization target.
Try with your AI agent
$ npm install -g pocketlantern $ pocketlantern init # Restart Claude Code, Cursor, or your MCP client, then ask: # "Should I upgrade to MariaDB 10.11 to 11.4 LTS Upgrade Planning now?"