[MXS-1756] Keep session consistent via session variable tracker Created: 2018-04-04 Updated: 2023-10-04 Resolved: 2023-10-04 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | N/A |
| Type: | New Feature | Priority: | Major |
| Reporter: | dapeng huang | Assignee: | Todd Stoffel (Inactive) |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Attachments: |
session_state_consistance.pptx
|
||||||||||||||||
| Issue Links: |
|
||||||||||||||||
| Description |
|
Let server told mxs the latest variable changes in ok packet, when mxs send result back to client ,at the same time, apply these changes to other backends; |
| Comments |
| Comment by markus makela [ 2018-06-12 ] |
|
If I understand this correctly, the idea is to execute all variable (mainly user variables) modifications on the master and propagate the results to the slaves. This would remove the need for the use_sql_variables_in parameter as well as improve overall performance of user variable modifications. |
| Comment by dapeng huang [ 2018-06-12 ] |
|
Yes, and also resolve the problem of routing all queries to master after multi stmts or stored procedure be executeed; |