[MXS-3882] Need some sort of shared cache or inter-maxscale communication for causal reads when multiple maxscales are used Created: 2021-11-16  Updated: 2021-11-17  Resolved: 2021-11-17

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

Type: New Feature Priority: Major
Reporter: Isaac Venn (Inactive) Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: triage

Issue Links:
Duplicate
duplicates MXS-3663 Causal Reads Global Cluster Distribution Closed

 Description   

Skysql currently allows for multiple maxscales to be deployed in a cluster. In the current configuration, the load balancer essentially round-robins between the two instances. As such, we believe that causal reads may not work as the queries could be split amongst the two instances.
Not sure if a shared cache, or some sort of communication between the maxscale instances would be required.



 Comments   
Comment by markus makela [ 2021-11-17 ]

I'm assuming this "breaks" only causal_reads=global as all other modes only retain the causality for queries done by the same connection.

Comment by markus makela [ 2021-11-17 ]

I'll close this as it seems to be a duplicate of MXS-3663.

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