[MXS-3344] Support statement pipelining of reads and multi-target queries Created: 2020-12-17  Updated: 2022-09-08  Resolved: 2022-09-08

Status: Closed
Project: MariaDB MaxScale
Component/s: readwritesplit
Affects Version/s: None
Fix Version/s: N/A

Type: New Feature Priority: Major
Reporter: markus makela Assignee: markus makela
Resolution: Won't Do Votes: 0
Labels: None

Issue Links:
Issue split
split from MXS-1245 Support statement pipelining Closed

 Description   

This is a continuation of MXS-1245.

With MXS-1245 implemented, queries that are routed to the master are executed in a streaming fashion. This can be relatively easily extended to cover queries that target slaves but the major hurdle with that is the target selection code has to be modified to be aware of it.

For multi-target queries the issue is more complex. In theory this is simple: append the command to the history and execute it on all backends. The replier for all the executed session commands should be the same server. The accounting of the session command history must be updated for this to be doable.

The problems come when different target types are mixed while streaming queries. The streaming of session commands and single-target queries can be done if the replying backend is the same as the replier of the session command.


Generated at Thu Feb 08 04:20:44 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.