Alexander Keremidarski added a comment - 2019-10-18 16:25 Upon upgrade from MySQL to MariaDB master-info-repository and relay-log-info-repository are completely ignored without even warning in .err log. This causes troubles when migrating slave servers. There should be at least warning if not error in .err log. Ideally mysql_upgrade script should take care of that and extract the data from mysql.slave_master_info and mysql.slave_relay_log_info to store them in master.info file.

Andrei Elkin added a comment - 2020-01-29 12:38 julien.fritsch : to why would it be possible to do.. - I merely offered an option if this feature request can be rated as a bug. After all no new option seem need to be provided for the user. But now when I dwelt into the matter better, the ultimate goal's changes in the upgrade script do not look significant at all. salle , how about executing a couple of sql queries on the MySQL slave side prior its ultimate stopping: set @ @global .master_info_repository= 'file' ; set @ @global .relay_log_info_repository= 'file' ; I am not sure where to place those lines but the mysql_upgrade docs leaves hope we can place them there and run the program twice - before and after the new binary are installed: mysql_upgrade is run after starting the new MariaDB server. Running it before you shut down the old version will not hurt anything and will allow you to make sure it works and figure out authentication for it ahead of time.

Sujatha Sivakumar (Inactive) added a comment - 2020-03-10 13:30 Code changes: https://github.com/MariaDB/server/commit/9ae015878f11be3e3033fd1b35357ea5927c6c51 Build Bot testing: http://buildbot.askmonty.org/buildbot/grid?category=main&branch=bb-10.5-sujatha Changes were reviewed and approved by Andrei.