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

replication testing: 5.6->10.0

        Details

        • Type: Task
        • Status: Stalled
        • Priority: Minor
        • Resolution: Unresolved
        • Fix Version/s: 10.0
        • Component/s: None
        • Labels:
          None

          Description

          We need to test to what extent replication from 5.6 to 10.0 works. That is what new replication features in 5.6 are understood by 10.0 and what aren't.

          These new replication features are at least:

          • New insert/update/delete row events (MDEV-5115)
          • event checksums (already in 5.2, backported from 5.6)
          • ignorable events (may be not supported, but have to be)
          • global transaction id (not supported)

          the list above is not exhaustive.

            Gliffy Diagrams

              Attachments

                Issue Links

                is blocked by

                Bug - A problem which impairs or prevents the functions of the product. MDEV-5765 Replication 5.6=>10.0 causes garbage data on slave if master has binlog_row_image=minimal

                • Major - Major loss of function.
                • Open

                Bug - A problem which impairs or prevents the functions of the product. MDEV-5767 Replication 5.6=>10.0 fails with binlog_rows_query_log_events=ON on master

                • Minor - Minor loss of function, or other problem where easy workaround is present.
                • Open

                Task - A task that needs to be done. MDEV-4487 FR: Allow replication from MySQL 5.6+ when GTID is enabled on the master

                • Minor - Minor loss of function, or other problem where easy workaround is present.
                • Open
                relates to

                Bug - A problem which impairs or prevents the functions of the product. MDEV-5769 Slave crashes on attempt to do parallel replication from an older master

                • Critical - Crashes, loss of data, severe memory leak.
                • Closed

                Bug - A problem which impairs or prevents the functions of the product. MDEV-5785 RBR between old master and new slave breaks on direct updates to system tables

                • Minor - Minor loss of function, or other problem where easy workaround is present.
                • Closed

                Bug - A problem which impairs or prevents the functions of the product. MDEV-5799 Error messages written upon LOST EVENTS incident are corrupted

                • Trivial - Cosmetic problem like misspelt words or misaligned text.
                • Closed

                Bug - A problem which impairs or prevents the functions of the product. MDEV-5115 RBR from MySQL 5.6 to MariaDB 10.0 does not work

                • Major - Major loss of function.
                • Closed

                Task - A task that needs to be done. MDEV-3823 Backport WL#5917 sufficient to be able to replicate row events from mysql 5.6 master with default options

                • Minor - Minor loss of function, or other problem where easy workaround is present.
                • Closed

                  Activity

                  Hide
                  Permalink
                  elenst Elena Stepanova added a comment -

                  The current status is that replication 5.6 => 10.0.9 works to some extent – if the master is not using non-default replication- modes or configuration, e.g. GTID, binlog_row_image and such.
                  This replication path can be used as an upgrade mechanism, if during the upgrade window the master does not write into the binary log any new syntax not merged into 10.0.

                  Related bugs can be found in "Issue links".

                  Show
                  elenst Elena Stepanova added a comment - The current status is that replication 5.6 => 10.0.9 works to some extent – if the master is not using non-default replication- modes or configuration, e.g. GTID, binlog_row_image and such. This replication path can be used as an upgrade mechanism, if during the upgrade window the master does not write into the binary log any new syntax not merged into 10.0. Related bugs can be found in "Issue links".

                    People

                    • Assignee:
                      elenst Elena Stepanova
                      Reporter:
                      serg Sergei Golubchik
                    • Votes:
                      0 Vote for this issue
                      Watchers:
                      6 Start watching this issue

                      Dates

                      • Created:
                        Updated: