Uploaded image for project: 'MariaDB MaxScale'
  1. MariaDB MaxScale
  2. MXS-1778

Consistent reads by the utlization of GTID in OK packet.

    XMLWordPrintable

Details

    • New Feature
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • None
    • 2.3.0
    • readwritesplit
    • None
    • MXS-SPRINT-58

    Description

      https://jira.mariadb.org/browse/MDEV-11956 will provide the last GTID in the OK packet. That can be utilized for providing consistent reads in the context of MaxScale and readwritesplit.

      When e.g. an UPDATE is performed on the master, MaxScale will store the GTID. When a SELECT comes along, MaxScale could inject SELECT MASTER_GTID_WAIT(xyz) before the actual SELECT, thus ensuring that whatever modifications the UPDATE caused, will be available when the actual SELECT is executed on the chosen slave.

      Attachments

        Issue Links

          Activity

            People

              markus makela markus makela
              johan.wikman Johan Wikman
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 10d
                  10d
                  Remaining:
                  Time Spent - 6.5h Remaining Estimate - 9d 1.5h
                  9d 1.5h
                  Logged:
                  Time Spent - 6.5h Remaining Estimate - 9d 1.5h
                  6.5h

                  Git Integration

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