[MDEV-33364] pre-uninstall scriptlets should use slow innodb shutdown for upgrades Created: 2024-02-02  Updated: 2024-02-02  Resolved: 2024-02-02

Status: Closed
Project: MariaDB Server
Component/s: Platform Debian, Platform RedHat, Storage Engine - InnoDB
Fix Version/s: N/A

Type: New Feature Priority: Major
Reporter: Sergei Golubchik Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: beginner-friendly

Issue Links:
Duplicate
duplicates MDEV-30755 slow shutdown on uninstall Open
Relates
relates to MDEV-23755 safety for upgrades (innodb) and pack... Closed

 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

 Comments   
Comment by Marko Mäkelä [ 2024-02-02 ]

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, in MDEV-15912 a 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.

Generated at Thu Feb 08 10:38:21 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.