Why is this marked as "Closed"? I didn't spot any place that would have the documentation for DBA's on how to do safe upgrades in the sense as marko suggests they should be done to avoid hitting certain bugs.

Until this documentation exists so a DBA can understand it, I cannot understand it either nor complete https://github.com/MariaDB/server/pull/1833.

greenman Why is this marked as "Closed"? I didn't spot any place that would have the documentation for DBA's on how to do safe upgrades in the sense as Marko Mäkelä suggests they should be done to avoid hitting certain bugs.

To be able to follow-up on bug reports, it would be good that when bugs are closed, there would be some link/trace of how/why it was closed. Thanks!

I think this was the edit

Thanks. Since that link is behind a login-wall, I'll post the update here for clarity:

This basically says that run `innodb_fast_shutdown=1` before upgrades to be safe, and the same rule applies for each and every MariaDB version. This seems much simpler than the elaborate description by marko in MDEV-23755.

otto, I think that the short version (shut down the old server, using the default value of innodb_fast_shutdown=1) should be good enough for most users.

One thing that might be useful to mention is that the DBA should ensure that no XA PREPARE transactions exist in the system before initiating the shutdown. Such transactions are being internally created by the binlog. I am not currently aware of problems related to that. I would expect that no internal XA transactions would never be left behind by the system. Distributed transactions (explicit use of XA statements by the user) were of very limited use until MDEV-742 was finally fixed in MariaDB Server 10.5.