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

Qlafilter message timing is inconsistent

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 6
    • Fix Version/s: 6.2.0
    • Component/s: qlafilter
    • Labels:
      None
    • Sprint:
      MXS-SPRINT-141

      Description

      Depending on the configuration, the messages are either logged before they start or after the first response is received. Logging the message only when it fully completes in all cases would make the latency measurement more accurate and provide similar semantics for the data in all cases. This also solves the problem where queries that fail due to network errors are logged but not really executed.

        Attachments

          Activity

            People

            Assignee:
            nantti Niclas Antti
            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.