[MXS-1778] Consistent reads by the utlization of GTID in OK packet. Created: 2018-04-11  Updated: 2018-05-28  Resolved: 2018-05-23

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

Type: New Feature Priority: Major
Reporter: Johan Wikman Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Blocks
is blocked by MDEV-11956 Get last_gtid in OK packet. Closed
is blocked by MDEV-15477 SESSION_SYSVARS_TRACKER does not trac... Closed
Sprint: MXS-SPRINT-58

 Description   

https://jira.mariadb.org/browse/MDEV-11956 will provide the last GTID in the OK packet. That can be utilized for providing consistent reads in the context of MaxScale and readwritesplit.

When e.g. an UPDATE is performed on the master, MaxScale will store the GTID. When a SELECT comes along, MaxScale could inject SELECT MASTER_GTID_WAIT(xyz) before the actual SELECT, thus ensuring that whatever modifications the UPDATE caused, will be available when the actual SELECT is executed on the chosen slave.


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