[MXS-14] Support GTID_WAIT Created: 2015-03-09 Updated: 2016-10-17 Resolved: 2016-10-17 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | Core |
| Affects Version/s: | None |
| Fix Version/s: | N/A |
| Type: | New Feature | Priority: | Major |
| Reporter: | VAROQUI Stephane | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Description |
|
Queuing read queries between 2 writes to define some read execution windows . Enable monitoring plugin to run in infinite loop and to execute gtid_wait of the the first GTID of the window. Routing module are enabled to execute on slave after the the gtid_wait return successfully, or execute on master if no backend monitor as succed with gtid_wait and faield in timeout |
| Comments |
| Comment by Johan Wikman [ 2016-10-17 ] |
|
This is a good idea. When a statement is sent to master, we could inject ; select @@gtid_current_pos after the statement, so that we would get the GTID. Then when a statement is sent to a slave we could inject select master_gtid_wait(gtid); before the actual statement. That way there would be no slavelag. |
| Comment by Johan Wikman [ 2016-10-17 ] |
|
Seems to be a duplicate of Retaining that one as it contains more information. |