Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-10047

table-based master info repository

    XMLWordPrintable

    Details

      Description

      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.

      The ticket description is edited to stress on the missed warnings at or after upgrade to mariadb, the former description text is below. In fact its aim to have table-based master info is addressed through mysql.gtid_slave_pos which in combination with {{CHANGE MASTER TO ... master_use_gtid = slave_pos }} provides failure tolerance to slave.

      I'd like to see MariaDB support table-based master info repository (see https://dev.mysql.com/doc/refman/5.6/en/replication-options-slave.html#option_mysqld_master-info-repository). If an InnoDB table were used, it could be encrypted. This would be preferable to having to put the password in plaintext in a text file.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              sujatha.sivakumar Sujatha Sivakumar
              Reporter:
              kolbe Kolbe Kegel (Inactive)
              Votes:
              9 Vote for this issue
              Watchers:
              16 Start watching this issue

                Dates

                Due:
                Created:
                Updated:
                Resolved: