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

Limit total number of connections to backend

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 6.3.0
    • Component/s: Core
    • Labels:
      None
    • Sprint:
      MXS-SPRINT-146, MXS-SPRINT-147, MXS-SPRINT-148, MXS-SPRINT-149, MXS-SPRINT-150, MXS-SPRINT-151, MXS-SPRINT-152

      Description

      When the MaxScale pooling feature is enabled, idle connections are put to a pool from which connections are taken when needed. However, if there are no connections in the pool, then a new backend connection will always created. Consequently, the presence of the pool does not provide an upper limit for the total number of backend connections.

      There are situations where providing an upper limit on the number of backend connections, while simultaneously not restricting the number of clients, is what is wanted. The pooling mechanism should be extended so that it also optionally would imply the maximum number of connections that are created.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              esa.korhonen Esa Korhonen
              Reporter:
              johan.wikman Johan Wikman
              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.