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

Delayed connection creation

    XMLWordPrintable

Details

    • New Feature
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 2.2.3
    • 2.4.0
    • readwritesplit
    • None
    • CentOS 7
      maxscale-2.2.3-1.x86_64

    Description

      Original description

      The readwritesprit router have specification called "Routing to every session backend" in this page.

      https://mariadb.com/kb/en/mariadb-enterprise/mariadb-maxscale-22-readwritesplit/

      For example, SET NAMES 'utf8' is always executed on the master server even if there is no write in the following statements.

      So, a slave server with a high load could make the master server in the error state of "Too many connections".

      I want a function that does not execute the session commands until it needs it.

      Implementation Notes

      This ties in with the improved storage of session commands so that the execution of session commands on the master can be postponed until a master connection is needed.

      Attachments

        Issue Links

          Activity

            People

              markus makela markus makela
              g980 sava
              Votes:
              1 Vote for this issue
              Watchers:
              3 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.