[MXS-1694] Support Redirect Mode Created: 2018-03-01 Updated: 2019-02-01 Resolved: 2019-02-01 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | Router |
| Affects Version/s: | 2.2.2 |
| Fix Version/s: | N/A |
| Type: | New Feature | Priority: | Minor |
| Reporter: | Thomas J. Girsch | Assignee: | Dipti Joshi (Inactive) |
| Resolution: | Won't Do | Votes: | 1 |
| Labels: | galera, maxscale, replication | ||
| Environment: |
CentOS 7 |
||
| 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. |
| Comments |
| Comment by Johan Wikman [ 2018-03-26 ] |
|
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. |
| Comment by Dipti Joshi (Inactive) [ 2018-04-10 ] |
|
This goes against MaxScale as a proxy layer that insulates clients from servers and servers from client. Hence not doing it. |
| Comment by Michael Widenius [ 2018-04-26 ] |
|
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! |
| Comment by markus makela [ 2018-04-26 ] |
|
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 |