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

idle_session_pool_time=0s doesn't immediately pool idle connections

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 6.1.1
    • Fix Version/s: 6.2.0
    • Component/s: Core
    • Labels:
      None

      Description

      When configured with idle_session_pool_time=0s, the connections will only be put into the
      pool once they have been idle longer than the configured time. Since the comparison is done at one second granularity, a connection would have to be idle for more than a second for it to be put into the pool.

      The interpretation of the value should be changed to use greater-than-or-equal semantics instead of the current greater-than semantics. Additionally, the granularity can be changed to use the internal ticks of 100 milliseconds.

        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.