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

Tracking active connection in Maxscale in order to comlete the full processlist table

    XMLWordPrintable

Details

    • New Feature
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • 24.02.2
    • None
    • maxgui, REST-API
    • None

    Description

      As requested by an existing MariaDB Enterprise customer, we are sometimes limited by a show full processlist, which will give us information such as the id, the user or the source ip, but if it goes through a maxscale, the source ip is replaced by that of maxscale (which makes sense).

      As a result, we have a loss of information because maxscale and mariadb-server can't make the link between the two. The aim would therefore be to have an equivalent of the X-FORWARDED-FOR of the http protocol, for example in MariaDB-server. We could imagine a vision like this:

      Id: 123456
      User: usermysql
      Host: maxscale:1234 (sourceserver:45678)
      db: myawesomedb
      Command: Sleep
      Time: 99999999
      State: starting
      Info: show full processlist
      Progress: 0.000

      A solution of this type would facilitate debugging and make it easier to find the source of the request.

      Attachments

        Activity

          People

            maxmether Max Mether
            sebastien.giraud Sebastien GIRAUD
            Votes:
            0 Vote for this issue
            Watchers:
            2 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.