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

GTID - do not do on-disk update of master.info after every event group

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 10.0.7
    • Component/s: None
    • Labels:

      Description

      In GTID mode, we should not update the master.info file after every
      transaction.

      Such update is pointless (we will delete the relay logs in any case at next
      slave start), and decreases performance. But the more serious issue is that if
      we crash during such update, we might end up with a partially written, and
      thus corrupt, state. This could in the worst case prevent slave restart
      (eg. if using_gtid flag got cleared), and thus breaks crash-safe slave promises.

      In addition, when we do write master.info, it could happen that the file gets
      shorter. In this case we need to make sure we do not leave old junk at the end
      of the file. Probably best is to just leave an end marker, beyond which no more
      data is valid.

        Attachments

          Activity

            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:

                Git Integration

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