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

MariaDB 10.0 statement-based events cannot be executed in parallel by MySQL 5.6

    Details

    • Type: Bug
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 10.0.16
    • Fix Version/s: N/A
    • Component/s: Replication
    • Labels:

      Description

      MySQL 5.6 parallel slave execution "doesn't work" on statement-based events from a MariaDB 10.0 master. Row-based events are correctly parallelized.

      Perhaps there is some difference in log format between MariaDB 10.0 and MySQL 5.6 that allows a MySQL 5.6 slave to identify the database(s) written to by a statement-based event when the event comes from a MySQL master, but that information is missing from the log written by a MariaDB 10.0 master?

        Gliffy Diagrams

          Attachments

            Activity

            Hide
            elenst Elena Stepanova added a comment -

            The lack of parallellism can be reproduced easily.
            Same happens with MySQL 5.5=>5.6 replication.

            I don't see anything obvious in the binlog (as parsed by mysqlbinlog). The only suspicious thing in the slave error log is the complaint about missing SERVER_UUID on master. It might be or be not the reason.

            Assigning to Kristian Nielsen who might be able to shed some light on it.

            Show
            elenst Elena Stepanova added a comment - The lack of parallellism can be reproduced easily. Same happens with MySQL 5.5=>5.6 replication. I don't see anything obvious in the binlog (as parsed by mysqlbinlog). The only suspicious thing in the slave error log is the complaint about missing SERVER_UUID on master. It might be or be not the reason. Assigning to Kristian Nielsen who might be able to shed some light on it.
            Hide
            knielsen Kristian Nielsen added a comment -

            One reason might be that the BEGIN query event that is sent to the MySQL 5.6 slave by the MariaDB 10.0 master does not contain the current schema/database. Nor is there any logical clock information sent.

            Show
            knielsen Kristian Nielsen added a comment - One reason might be that the BEGIN query event that is sent to the MySQL 5.6 slave by the MariaDB 10.0 master does not contain the current schema/database. Nor is there any logical clock information sent.

              People

              • Assignee:
                knielsen Kristian Nielsen
                Reporter:
                kolbe Kolbe Kegel
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated: