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

Causal Reads Global Cluster Distribution

    XMLWordPrintable

Details

    • New Feature
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • None
    • 22.08.0
    • readwritesplit
    • None
    • 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

          is duplicated by

          New Feature - A new feature of the product, which has yet to be developed. MXS-3882 Need some sort of shared cache or inter-maxscale communication for causal reads when multiple maxscales are used

          • Major - Major loss of function.
          • Closed

          New Feature - A new feature of the product, which has yet to be developed. MXS-3884 Multiple maxscales should share state for global causal reads

          • Major - Major loss of function.
          • Closed

          Activity

            People

              markus makela markus makela
              toddstoffel Todd Stoffel (Inactive)
              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.