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

Phase 3 Research: Write Through Cache

    XMLWordPrintable

Details

    • Task
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • None
    • None
    • None
    • None

    Description

      We need to better understand how gridgain Write Through Cache could work

      • what are the sql differences that could have larger architecture implications. The cost of missing wrong / caching wrong values.
      • better understanding what gridgain cant do and how that impacts write through
      • what is configured in gridgain to write through to mariadb
      • how would gridgain handle failover of a primary (mariadb server) write through
      • what is needed from maxscale to use gridgain for write through
      • client -> maxscale -> gridgain -> server vs
      • client -> gridgain -> maxscale -> server
      • determine which connector to use between maxscale -> gridgain
      • how gridgain handles mariadb protocol and what should we do about it

      Attachments

        Activity

          People

            Unassigned Unassigned
            allen.herrera Allen Herrera
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:

              Git Integration

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