[MXS-185] "read-only" transactions to be directed to the slaves by the readwritesplit router Created: 2015-06-09 Updated: 2022-02-02 Resolved: 2017-01-25 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | readwritesplit |
| Affects Version/s: | 1.1.0 |
| Fix Version/s: | 2.1.0 |
| Type: | New Feature | Priority: | Major |
| Reporter: | Stoykov (Inactive) | Assignee: | Massimiliano Pinto (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | readwritesplit | ||
| Issue Links: |
|
||||||||
| Sprint: | 2017-26 | ||||||||
| Description |
|
As per the recent status of the Current Release: 1.1.0 , MaxScale readwritesplit router routes all queries wrapped in a transaction to the master. It will be good to detect the "READ ONLY" transactions and to be able to direct them to the available slaves. |
| Comments |
| Comment by Dipti Joshi (Inactive) [ 2015-08-04 ] |
|
markus makelaCan you comment on this please ? |
| Comment by markus makela [ 2015-08-04 ] |
|
Should be somewhat easy to implement as long as START TRANSACTION READ ONLY is used. If not, then it would require some other mechanism to detect read-only transactions, possibly with MaxScale's routing hints. |
| Comment by Dipti Joshi (Inactive) [ 2015-09-15 ] |
|
markus makela Since the fixVersion for this feature is 1.4.0 - Please let us make sure we do not start this work until after 1.3.0 is released |
| Comment by Johan Wikman [ 2016-05-31 ] |
|
Removed Fix-Version. Not clear at this point if/when this could be implemented. |
| Comment by Massimiliano Pinto (Inactive) [ 2017-01-25 ] |
|
START TRANSACTION READ ONLY is detected and all included statements and COMMIT or ROLLBACK are routed to the same slave server |