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

Porting Rdb_binlog_manager to MariaDB

    Details

      Description

      Looking at Rdb_binlog_manager in FB/MySQL.

      Feature 1: store the master position in MyRocks

      It stores the master position in this record:

      key: BINLOG_INFO_INDEX_NUMBER
      value:  
        - binlog_file:position
        - Last GTID (isn't that a function of binlog position?)
      

      Uses for that information:

      • It is visible through INFORMATION_SCHEMA.ROCKSDB_GLOBAL_INFO.

      Re #2, InnoDB in FB/MySQL has similar code in is_binlog_advanced (and MariaDB's InnoDB doesn't have it)

      Feature 2: keep mysql.slave_gtid_info up to date

      When slave-gtid-info=optimized option is used, mysql.slave_gtid_info is kept up-todate directly by the storage engines. (See https://github.com/facebook/mysql-5.6/commit/0f402cb8381ba9d8e71c93085a22e5a12589b6e3)

      (Q: and that option is not used, both the SE and the SQL layer do the updates?)

      Proposed solution

      • Neither of the above features are essential (or storage engine-only)
      • MariaDB has an error when trying to use a part of Rdb_binlog_manager (as it doesn't have binlog position stored). We need to disable it.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                psergey Sergei Petrunia
                Reporter:
                psergey Sergei Petrunia
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated: