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

Allow dirty reads/writes

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 2.4.2
    • Fix Version/s: Icebox
    • Component/s: galeramon
    • Labels:
      None
    • Environment:
      ALL

      Description

      As of today Maxscale doesn't care for gcs.ignore_sb and wsrep_ditry_reads settings.

      This means in many cases Maxscale becomes an issue for tpopologies since client can only have 2 states : working and incident and nothing in between where apps can keep reading datas in case of an incident. this is more than usefull in settings where we want to minimize downtime on reads to the very strict minimum.

        Attachments

          Activity

            People

            Assignee:
            toddstoffel Todd Stoffel
            Reporter:
            SylvainArbaudie Sylvain ARBAUDIE
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated: