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

Auto READ request routing to MASTER if slaves are lagging behind

    XMLWordPrintable

Details

    • New Feature
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • None
    • 2.3.1
    • readwritesplit
    • None

    Description

      The customer expects MaxScale to take care of the routing of queries internally which it does, also if all the slaves are lagging behind or the GTIDs are not yet caught up to Master, The "READ" queries should automatically be routed to The Master DB node.

      This is to simplify the application design so that app team doesn't need to worry about getting outdated data reads from SLAVES.

      Attachments

        Activity

          People

            markus makela markus makela
            Faisal Faisal Saeed (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 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.