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

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

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Minor
    • Resolution: Fixed
    • 10.0.4
    • None
    • None
    • 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.

      Attachments

        Activity

          People

            knielsen Kristian Nielsen
            knielsen Kristian Nielsen
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.