Details
-
New Feature
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Duplicate
Description
innodb fast shutdown is not necessarily safe over upgrades, the documentation recommends to do
set global innodb_fast_shutdown=0; |
before upgrading MariaDB.
It can be automated, in case of apt upgrade mariadb-server or dnf upgade MariaDB-server, the pre-install scriptlet of the old server version can tell the server to use slow shutdown, if it's an uninstall for an upgrade
Attachments
Issue Links
- duplicates
-
MDEV-30755 slow shutdown on uninstall
-
- Open
-
- relates to
-
MDEV-23755 safety for upgrades (innodb) and packaging
-
- Closed
-
This seems to duplicate MDEV-30755 and contradict with what was found and documented in
MDEV-23755. Do we really need this?For some time, it was somewhat unclear whether it is safe to upgrade to MariaDB Server 10.3 from earlier versions after a normal shutdown. It was possible to get into trouble by playing with innodb_force_recovery=3 (
MDEV-13269). Finally, inMDEV-15912a check for that was implemented: InnoDB would refuse to start if it recovers any incomplete transactions that contain nonempty insert undo logs.Recently, there were some upgrade issues related to
MDEV-29694, which could be worked around by executing a slow shutdown. These bugs have been fixed.