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

Handling of queries by SmartRouter when Exasol or GridGain is unavailable

    XMLWordPrintable

Details

    • New Feature
    • Status: In Progress (View Workflow)
    • Major
    • Resolution: Unresolved
    • 25.10, 26.10
    • 26.10.1
    • None
    • None

    Description

      When Exasol or GridGain is unavailable, SmartRouter still routes to it the queries that it has measured to be faster there, and the session is then closed. A query that a hint routes to Exasol or GridGain also closes the session.

      A read that times out waiting for a cluster when causal_reads is used is instead handled according to causal_reads_on_timeout: it is routed to the primary or answered with an error, and the session remains usable. There is no corresponding choice when the target is unavailable, although executing a query that is best handled by an analytical engine on the primary may be very expensive.

      Attachments

        Issue Links

          Activity

            People

              johan.wikman Johan Wikman
              johan.wikman Johan Wikman
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:

                Time Tracking

                  Estimated:
                  Original Estimate - 3d
                  3d
                  Remaining:
                  Time Spent - 1h Remaining Estimate - 2d 7h
                  2d 7h
                  Logged:
                  Time Spent - 1h Remaining Estimate - 2d 7h
                  1h

                  Git Integration

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