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

More precise binlog position reporting for IO thread when reconnecting with GTID

        Details

        • Type: Bug
        • Status: Closed
        • Priority: Minor
        • Resolution: Duplicate
        • Affects Version/s: 10.0.4
        • Fix Version/s: None
        • Component/s: None
        • Labels:
          None

          Description

          As reported by Pavel Ivanov:

          https://lists.launchpad.net/maria-developers/msg06216.html
          https://lists.launchpad.net/maria-developers/msg06246.html

          The scenario is that IO thread is using GTID to find the starting position
          when connecting to the master. In case of re-connect in the middle of an event
          group, the IO thread needs to skip already received events following the GTID
          event of the reconnect starting position.

          The bug is that when reconnect happens at the end of an event group, the IO
          thread actually re-connects from the start of that event group, even though it
          could start from the next event group. This does not cause wrong behaviour
          (the event group is fetched and skipped as it should), however it causes
          reporting of GTID position in error log and old-style positions read from teh
          relay log to be a bit off, which could be confusing to users.

            Gliffy Diagrams

              Attachments

                Activity

                Hide
                Permalink
                knielsen Kristian Nielsen added a comment -

                Duplicate of MDEV-5130

                Show
                knielsen Kristian Nielsen added a comment - Duplicate of MDEV-5130

                  People

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

                    Dates

                    • Created:
                      Updated:
                      Resolved: