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

Causal Reads Global Cluster Distribution

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 22.08.0
    • Component/s: readwritesplit
    • Labels:
      None
    • Sprint:
      MXS-SPRINT-146, MXS-SPRINT-147, MXS-SPRINT-148, MXS-SPRINT-149

      Description

      Causal reads currently only works in a single MaxScale instance environment however for the purposes of HA, many customers are running multiple MaxScale servers. If the application is going though a load balancer like F5 or NLB, those connections are round robin'd to the various MaxScale instance and the benefit of causal reads is lost.

      We should devise a strategy to sync that information among MaxScale nodes.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              markus makela markus makela
              Reporter:
              toddstoffel Todd Stoffel
              Votes:
              2 Vote for this issue
              Watchers:
              7 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.