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

KILL commands leave no trace in the log

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Trivial
    • Resolution: Fixed
    • Affects Version/s: 2.5.19, 6.2.1
    • Fix Version/s: 2.5.20, 6.2.3
    • Component/s: Core
    • Labels:
      None

      Description

      Executing a KILL command through MaxScale causes some special code to be executed that handles the translation from the session ID used in MaxScale to the real connection ID on the backend servers. As this involves a set of relatively complicated steps, logging some messages on the info log level would help verify that it behaves as expected. Currently there are no messages logged at all for anything related to KILL queries.

        Attachments

          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.