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

MaxScale always advertises the SESSION_TRACK capability even with servers that don't support it (XPand)

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.5.12
    • Fix Version/s: 2.5.15, 6.1.2
    • Component/s: Core
    • Labels:
      None

      Description

      If MaxScale is used with a XPand cluster, which doesn't support all the newer features that were introduced after MySQL 5.0, a client that expects the SESSION_TRACK functionality to work will not receive it. This also appears to be a problem with DBeaver which seems to query session_track_schema during its connection phase.

      The solution is to check if any of the servers used by a service doesn't support the SESSION_TRACK capability and disable it if there is one.

        Attachments

          Issue Links

          is caused by

          Bug - A problem which impairs or prevents the functions of the product. MXS-3533 MaxScale doesn't advertise the SESSION_TRACK capability

          • Major - Major loss of function.
          • Closed

            Activity

              People

              Assignee:
              markus makela markus makela
              Reporter:
              markus makela markus makela
              Votes:
              0 Vote for this issue
              Watchers:
              1 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.