Details

    Description

      Currently, MaxScale operates only as a proxy, which enables many advanced features, but comes with the drawback of requiring twice the network traffic, since everything must go client->maxscale->db and vice versa. It would be helpful in some use cases to have the clients get routed directly to the DB, such that they only hit the MaxScale server at connect time; the MaxScale server would instruct them to go directly to a particular DB server, based on rules set up in the configuration file, and from then on, for the life of that session, all communication is directly between the client and the DB, without MaxScale involved.

      Attachments

        Activity

          johan.wikman Johan Wikman added a comment -

          As far as I can tell it would require awareness from the connector. When a connector that announces some particular capability connects, MaxScale would then not perform the usual activities that are performed at connection time, but would reply with some redirect message containing information about what IP the connector subsequently, silently behind the scenes, should connect to. That the connector has not connected to the IP the client requested but to some other IP would then, as far as I can tell, have to be hidden from the client.

          johan.wikman Johan Wikman added a comment - As far as I can tell it would require awareness from the connector. When a connector that announces some particular capability connects, MaxScale would then not perform the usual activities that are performed at connection time, but would reply with some redirect message containing information about what IP the connector subsequently, silently behind the scenes, should connect to. That the connector has not connected to the IP the client requested but to some other IP would then, as far as I can tell, have to be hidden from the client.

          This goes against MaxScale as a proxy layer that insulates clients from servers and servers from client. Hence not doing it.

          dshjoshi Dipti Joshi (Inactive) added a comment - This goes against MaxScale as a proxy layer that insulates clients from servers and servers from client. Hence not doing it.

          The argument that MaxScale is "just a proxy" is not good enough as this is a feature that can give great benefit to some of our users!

          monty Michael Widenius added a comment - The argument that MaxScale is "just a proxy" is not good enough as this is a feature that can give great benefit to some of our users!
          markus makela markus makela added a comment - A possible minimal implementation is described here: https://jira.mariadb.org/browse/MDEV-15935?focusedCommentId=110228&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-110228

          People

            dshjoshi Dipti Joshi (Inactive)
            tgirsch Thomas J. Girsch
            Votes:
            1 Vote for this issue
            Watchers:
            7 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.