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

MaxScale leaks sessions if they are closed when writeq throttling is enabled

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 2.5.24, 6.4.5, 22.08.4
    • 2.5.25, 6.4.6, 22.08.5
    • Core
    • None

    Description

      The following Connector-J test case reproduces the problem. It only happens if writeq_high_water is lower than max_allowed_packet on the server. Due to the recent changes to the default values, this is unlikely to happen in older versions if the default values are used.

      -Dtest=integration.PreparedStatementParametersTest#bigSendError
      

      A workaround to this is to use the old default value for writeq_high_water. It won't eliminate the problem but it helps reduce the likelihood of it happening. Disabling the writeq throttling completely will prevent it but that can cause extreme memory usage.

      Attachments

        Activity

          People

            markus makela markus makela
            markus makela markus makela
            Votes:
            0 Vote for this issue
            Watchers:
            2 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.