maria-discuss team mailing list archive

[Artem Russakovskii <archon810@xxxxxxxxx>]

Hi,

This is my first post to the mariadb list, as I just migrated from mysql to
mariadb (OpenSUSE stopped supporting mysql after Leap 15.0).

I immediately ran into an issue migrating, with the slave not starting.
Upon further analysis, it turned out to be the lack of support of
master_info_repository=TABLE and relay_log_info_repository=TABLE in
mariadb, which means the master information effectively disappeared as far
as the slave server is concerned.

I am very surprised by this revelation. Not only did it break replication
(I had to figure this out and reassemble the CHANGE MASTER TO command with
the values fished out from the slave_master_info table), it also seems to
be a step back when it comes to crash-safe replication.

Does anyone have an explanation for why we're now back to master.info and
relay-log.info on disk rather than nice tables in memory?

See
https://www.percona.com/blog/2013/09/13/enabling-crash-safe-slaves-with-mysql-5-6/
from years ago for more info, for example.

It'd be great to hear from the core mariadb/mysql developers.

The lack of master_info_repository and relay_log_info_repository support is
documented here:
https://mariadb.com/kb/en/library/system-variable-differences-between-mariadb-102-and-mysql-56/
.

Thank you.

Sincerely,
Artem