Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Incomplete
-
None
Description
Hello,
One thing that has been keeping me reluctant of upgrading from MariaDB 10.5 to one of the latest versions (10.7~10.9) is because of the support/EOL of those versions being only 1 year.
10.5 => 24 Jun 2025
10.6 => 06 Jul 2026
10.7 => 14 Feb 2023
10.8 => 20 May 2023
10.9 => likely to follow same pattern (1 year)
I can understand why it's being done like that.
However, the problem is that the Upgrade process isn't comfortable enough to accommodate for these short EOL dates.
-
To upgrade a major version, I need to:
1) Make sure the my.cnf file is compatible with version I'm upgrading to (variables removed, etc)
2) Put website maintenance page (downtime)
3) Shut down MariaDB server (downtime)
4) Uninstall current version (downtime)
5) Install new version (downtime)
6) Start MariaDB server (downtime)
7) Run mysql_upgrade (downtime)
8) Hope that everything went smoothly, and remove website maintenance page
-
Having to do this every year just so that we keep Support active is unfortunately "not acceptable" if you must be 24 hours online.
Minor versions aren't so bad, because we just need a quick restart after updating the rpm, every few months.
Any thoughts on this?
Do you have other suggestions, or is there something I'm not thinking well about?
Thank you very much!