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

Add support for KILL QUERY <id>

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.2.0
    • Fix Version/s: 2.2.0
    • Component/s: Core
    • Labels:
      None

      Description

      When a KILL QUERY <id> is executed, MaxScale must change the ID given in the statement to the corresponding connection ID on the correct backend. This can be done by creating a one-to-many relation of internal session IDs to backend server IDs.

      All of the information required to implement this, namely the connection ID, is already collected by MaxScale and only the mapping of these IDs needs to be added. The problematic part is how to expose the session ID mapping in a consistent way.

        Attachments

          Issue Links

            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.